August 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2144) Automatic election & configuration of Master indexing node for each index

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2144: ------------------------------------- Summary: Automatic election & configuration of Master indexing node for each index Key: ISPN-2144 URL: https://issues.jboss.org/browse/ISPN-2144 Project: Infinispan Issue Type: Enhancement Components: Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.2.0.ALPHA2 It's currently overly complex to configure the master/slave configuration in Infinispan Query as it was designed for Hibernate Search. Especially different, in the case of Infinispan people should not have to deal with JMS, a secondary JGroups channel, nor static configuration for which node is the master. Infinispan has custom commands which can replace the communication channel, and an implementation of an auto-election policy is trivial. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
6
0 / 0

[JBoss JIRA] (ISPN-1862) fire TransactionCompletedEvent not as part of the transaction

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-1862: ---------------------------------- Summary: fire TransactionCompletedEvent not as part of the transaction Key: ISPN-1862 URL: https://issues.jboss.org/browse/ISPN-1862 Project: Infinispan Issue Type: Enhancement Components: Core API Affects Versions: 5.1.1.FINAL Reporter: Thomas Fromm Assignee: Manik Surtani When catching TransactionCompletedEvent I would expect, the transaction is committed, especially when isTransactionSuccessful() == true. I need to perform some operations after a transaction was completed. My workaround is ATM to suspend the transaction, perform my (async) stuff, and resume it afterwards. But in case of errors after resume, I get another TransactionCompletedEvent for this transaction with isTransactionSuccessful() == false. You see, I need something like a TransactionReallyCompletedEvent :-) My change request is, that the TransactionCompletedEvents should be fired, after the transaction was committed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (ISPN-1424) Implement non-blocking state transfer again on top of push-based state transfer

by Dan Berindei (JIRA)

Implement non-blocking state transfer again on top of push-based state transfer ------------------------------------------------------------------------------- Key: ISPN-1424 URL: https://issues.jboss.org/browse/ISPN-1424 Project: Infinispan Issue Type: Feature Request Components: State transfer Affects Versions: 5.0.1.FINAL Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.2.0.FINAL Once we have the asymmetric caches support in we should be able to re-implement non-blocking state transfer. See the design document at http://community.jboss.org/wiki/AsymmetricCachesAndManualRehashingDesign#... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
2
0 / 0

[JBoss JIRA] (ISPN-2232) Cache::start doesn't setup CommandInitializer in ComponentRegistry when used with Query

by Ales Justin (JIRA)

Ales Justin created ISPN-2232: --------------------------------- Summary: Cache::start doesn't setup CommandInitializer in ComponentRegistry when used with Query Key: ISPN-2232 URL: https://issues.jboss.org/browse/ISPN-2232 Project: Infinispan Issue Type: Feature Request Components: Configuration, Querying Affects Versions: 5.2.0.ALPHA2 Reporter: Ales Justin Assignee: Galder Zamarreño Fix For: 5.2.0.Alpha3 When re-starting existing stopped cache, NPE is thrown: 23:10:27,160 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (http-/192.168.1.101:8080-2) Exception sending request initialized lifecycle event to listener instance of class org.jboss.capedwarf.appidentity.GAEListener: java.lang.NullPointerException at org.infinispan.query.impl.LifecycleManager.cacheStarted(LifecycleManager.java:125) at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:178) [infinispan-core-5.2.0.ALPHA2.jar:5.2.0.ALPHA2] at org.infinispan.CacheImpl.start(CacheImpl.java:523) [infinispan-core-5.2.0.ALPHA2.jar:5.2.0.ALPHA2] at org.infinispan.AbstractDelegatingCache.start(AbstractDelegatingCache.java:343) [infinispan-core-5.2.0.ALPHA2.jar:5.2.0.ALPHA2] at org.jboss.capedwarf.common.infinispan.InfinispanUtils.checkCache(InfinispanUtils.java:72) [capedwarf-common-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] at org.jboss.capedwarf.common.infinispan.InfinispanUtils.getCache(InfinispanUtils.java:82) [capedwarf-common-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] This is the code I added: private static <K, V> Cache<K, V> checkCache(String cacheName) { final Cache<K, V> cache = cacheManager.getCache(cacheName, false); if (cache != null) { final ComponentStatus status = cache.getStatus(); if (status != ComponentStatus.INITIALIZING && status != ComponentStatus.RUNNING) { cache.start(); } } return cache; } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

4
18
0 / 0

[JBoss JIRA] (ISPN-2231) SyncReplTest#testMixingSyncAndAsyncOnSameTransport() looks to be broken

by Tomas Sykora (JIRA)

Tomas Sykora created ISPN-2231: ---------------------------------- Summary: SyncReplTest#testMixingSyncAndAsyncOnSameTransport() looks to be broken Key: ISPN-2231 URL: https://issues.jboss.org/browse/ISPN-2231 Project: Infinispan Issue Type: Bug Reporter: Tomas Sykora Assignee: Tristan Tarrant Please see https://github.com/infinispan/infinispan/blob/master/core/src/test/java/o.... When we switch lines 205 and 219 it pass with no problem. I expect that this shouldn't pass. The problem is - how we can properly test weather replication call was SYNC or ASYNC. Assigning to Tristan (or Marcus? familiar with mockito..) according to Manik's answer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

4
6
0 / 0

[JBoss JIRA] (ISPN-2239) Upgrade to JGroups 3.2.0.Alpha1

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2239: -------------------------------------- Summary: Upgrade to JGroups 3.2.0.Alpha1 Key: ISPN-2239 URL: https://issues.jboss.org/browse/ISPN-2239 Project: Infinispan Issue Type: Component Upgrade Reporter: Galder Zamarreño Assignee: Mircea Markus Fix For: 5.2.0.Alpha3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
2
0 / 0

[JBoss JIRA] (ISPN-2213) Query timeout support

by Marko Lukša (JIRA)

Marko Lukša created ISPN-2213: --------------------------------- Summary: Query timeout support Key: ISPN-2213 URL: https://issues.jboss.org/browse/ISPN-2213 Project: Infinispan Issue Type: Feature Request Components: Querying Reporter: Marko Lukša Assignee: Sanne Grinovero Since Hibernate Search supports setting a timeout for queries, Infinispan queries should support them, too. The support should also include a way to define the QueryTimeoutExceptionFactory used for producing the exception when a timeout occurs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
5
0 / 0

[JBoss JIRA] (ISPN-2094) New Configuration Changes do not work properly for multi file overrides

by William Burns (JIRA)

William Burns created ISPN-2094: ----------------------------------- Summary: New Configuration Changes do not work properly for multi file overrides Key: ISPN-2094 URL: https://issues.jboss.org/browse/ISPN-2094 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.2.0.ALPHA1 Reporter: William Burns Assignee: Manik Surtani In 5.1.3 I had helped provide a way for a user to pass in multiple infinispan.xml files at once to the parser. This was added with ISPN-1837. The configuration was now changed again with ISPN-1977, which moves it over to using the staxmapper. This works fine for cache overrides with named caches. However the problem is that the overrides do not function properly for default caches. The problem is that each named cache is made after every single file. At the point of creation the named cache picks up the sofar configured default cache. This means that the named cache will not have the default values of subsequent files. Unfortunately, I do not know if this can be fixed while still using the staxmapper. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

5
23
0 / 0

[JBoss JIRA] (ISPN-2243) Cache API bulk get method

by Robert Stupp (JIRA)

Robert Stupp created ISPN-2243: ---------------------------------- Summary: Cache API bulk get method Key: ISPN-2243 URL: https://issues.jboss.org/browse/ISPN-2243 Project: Infinispan Issue Type: Enhancement Components: Core API Reporter: Robert Stupp Assignee: Mircea Markus Please add a method like Map<K,V> bulkGet(Collection<K> keys); on the Cache or BasicCache interface. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
1
0 / 0

[JBoss JIRA] (ISPN-2087) Listen for state transfer events to keep indexes in sync with datacontainers

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2087: ------------------------------------- Summary: Listen for state transfer events to keep indexes in sync with datacontainers Key: ISPN-2087 URL: https://issues.jboss.org/browse/ISPN-2087 Project: Infinispan Issue Type: Feature Request Components: Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.2.0.ALPHA1 When the index is not shared across nodes but is supposed to contain only the data being owned by the node, we need to keep this data in sync when the view changes. See also https://community.jboss.org/docs/DOC-18370 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2012