September 2011 - infinispan-issues

[JBoss JIRA] Created: (ISPN-1191) Replace JGroups partial state transfer

by Vladimir Blagojevic (JIRA)

Replace JGroups partial state transfer -------------------------------------- Key: ISPN-1191 URL: https://issues.jboss.org/browse/ISPN-1191 Project: Infinispan Issue Type: Task Components: State transfer Affects Versions: 5.0.0.BETA2, 5.0.0.BETA1 Reporter: Vladimir Blagojevic Assignee: Manik Surtani Fix For: 5.0.0.FINAL We should investigate dropping partial state transfer as per our discussions at http://lists.jboss.org/pipermail/infinispan-dev/2011-June/008538.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (ISPN-1330) Update to version 0.2 of JCACHE API

by Kevin Pollet (JIRA)

Update to version 0.2 of JCACHE API ----------------------------------- Key: ISPN-1330 URL: https://issues.jboss.org/browse/ISPN-1330 Project: Infinispan Issue Type: Task Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Fix For: 5.1.0.BETA1, 5.1.0.FINAL This update will include: * the alignment of the implementation with the API changes * the support of {{@CacheKeyParam}} and {{@CachePut}} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-1321) Speedup AbstractComponentRegistry.invokeInjectionMethod()

by Sanne Grinovero (JIRA)

Speedup AbstractComponentRegistry.invokeInjectionMethod() --------------------------------------------------------- Key: ISPN-1321 URL: https://issues.jboss.org/browse/ISPN-1321 Project: Infinispan Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Manik Surtani Priority: Optional Fix For: 5.1.0.BETA1 As described on the forum reference, this method can slow down the boot process when there are many caches defined. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
9
0 / 0

[JBoss JIRA] Created: (ISPN-1390) Upgrade to JGroups 3.0

by Galder Zamarreño (JIRA)

Upgrade to JGroups 3.0 ---------------------- Key: ISPN-1390 URL: https://issues.jboss.org/browse/ISPN-1390 Project: Infinispan Issue Type: Component Upgrade Components: RPC Reporter: Galder Zamarreño Assignee: Dan Berindei Priority: Blocker Fix For: 5.1.0.BETA1, 5.1.0.FINAL AS 7.1 will have JGroups 3.0, so Infinispan needs to move to this version ASAP -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-1194) Consolidate rehash and replication state retrieval code

by Manik Surtani (JIRA)

Consolidate rehash and replication state retrieval code ------------------------------------------------------- Key: ISPN-1194 URL: https://issues.jboss.org/browse/ISPN-1194 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache, State transfer Affects Versions: 5.0.0.FINAL Reporter: Manik Surtani Assignee: Dan Berindei Priority: Blocker Fix For: 5.1.0.BETA1, 5.1.0.Final As discussed. Abstract the actual code that handles moving of state so that it can be used both for rehashing as well as state transfer for replicated caches, thereby removing dependence on JGroups' FLUSH and partial state transfer. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (ISPN-1216) Separate delimiter processing lock timeouts in state transfer

by Galder Zamarreño (JIRA)

Separate delimiter processing lock timeouts in state transfer ------------------------------------------------------------- Key: ISPN-1216 URL: https://issues.jboss.org/browse/ISPN-1216 Project: Infinispan Issue Type: Enhancement Components: State transfer Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.FINAL It appears that majority of EOFException instances encountered during state transfer are due to lock acquisition problem in the processing lock. So, consider adding a different limiter when the processing lock timeout is encountered. This should allow the receiving end to know more about the exact problem encountered by the sender side and so could provide more hints to the user. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
5
0 / 0

[JBoss JIRA] Created: (ISPN-1376) Upgrade Lucene Directory to support Lucene 3.4.0

by Sanne Grinovero (JIRA)

Upgrade Lucene Directory to support Lucene 3.4.0 ------------------------------------------------ Key: ISPN-1376 URL: https://issues.jboss.org/browse/ISPN-1376 Project: Infinispan Issue Type: Enhancement Components: Lucene Directory Reporter: Sanne Grinovero Assignee: Sanne Grinovero -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-1388) Eviction scheduled executor never shutdown

by Galder Zamarreño (JIRA)

Eviction scheduled executor never shutdown ------------------------------------------ Key: ISPN-1388 URL: https://issues.jboss.org/browse/ISPN-1388 Project: Infinispan Issue Type: Bug Components: Eviction Affects Versions: 5.0.1.FINAL Reporter: Galder Zamarreño Assignee: Galder Zamarreño Priority: Critical Fix For: 5.1.0.ALPHA2 , 5.1.0.FINAL Attachments: threaddump.txt At the end of the testsuite, there're about ~900 scheduled eviction threads lying around. Is the scheduled eviction executor thread shutdown at all??? What's not very clear here is whose responsibility is to shutdown executor services. For example, take @ComponentName(ASYNC_TRANSPORT_EXECUTOR), this is injected into: CacheImpl, RpcManagerImpl, QueryInterceptor and JGroupsTransport. Who's supposed to shut it down? Right now, it's RpcManagerImpl doing it, which is a named cache component. This opens another interesting question: Are ExecutorService components global, or per cache? Or both? For example, take ASYNC_TRANSPORT_EXECUTOR, it's injected to Transport, so must be global. But then you see RpcManagerImpl, which is a named cache component shutting it down? Surely that cannot be right. Going back to the original concern, take KnownComponentNames.EVICTION_SCHEDULED_EXECUTOR which is used by EvictionManagerImpl, this is never shutdown by anyone, which matches what's seen in the thread dump. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-1386) Nodes stopping can be merged without a reduced view being installed

by Galder Zamarreño (JIRA)

Nodes stopping can be merged without a reduced view being installed ------------------------------------------------------------------- Key: ISPN-1386 URL: https://issues.jboss.org/browse/ISPN-1386 Project: Infinispan Issue Type: Bug Components: Test Suite Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.ALPHA2 The attached log is showing a test failure because a view is not stablished with the two remaining nodes: {code}2011-09-14 13:01:15,124 ERROR (testng-TopologyInfoBroadcastTest) [org.infinispan.test.fwk.UnitTestTestNGListener] Method testNodeLeaves(org.infinispan.distribution.topologyaware.TopologyInfoBroadcastTest) threw an exception java.lang.RuntimeException: Timed out before caches had complete views. Expected 2 members in each view. Views are as follows: [[TopologyInfoBroadcastTest-NodeA-20211(s0), TopologyInfoBroadcastTest-NodeB-32215(s1), TopologyInfoBroadcastTest-NodeC-36650(s2)], [TopologyInfoBroadcastTest-NodeA-20211(s0), TopologyInfoBroadcastTest-NodeB-32215(s1), TopologyInfoBroadcastTest-NodeC-36650(s2)]] {code} Having glanced some TRACE logs captured by Dan, it would appear that as NodeB is shutting down, TEST_PING finds it as a sole cluster member and finds another cluster formed of NodeA,NodeC, leading to a merge. This is somehow stopping a correct 2-node view being installed. Needs further investigation -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
8
0 / 0

[JBoss JIRA] Created: (ISPN-1229) Use ProtocolStackConfigurator to edit the JGroups configuration instead of regular expressions

by Dan Berindei (JIRA)

Use ProtocolStackConfigurator to edit the JGroups configuration instead of regular expressions ---------------------------------------------------------------------------------------------- Key: ISPN-1229 URL: https://issues.jboss.org/browse/ISPN-1229 Project: Infinispan Issue Type: Enhancement Components: Test Suite Affects Versions: 5.0.0.CR7 Reporter: Dan Berindei Assignee: Manik Surtani Priority: Minor Fix For: 5.1.0.Final JGroupsConfigBuilder uses regular expressions to modify the JGroups protocol configuration, it should use the JGroups programmatic configuration support instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2011