September 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2093) State transfer taking too long on node join

by Michal Linhard (JIRA)

Michal Linhard created ISPN-2093: ------------------------------------ Summary: State transfer taking too long on node join Key: ISPN-2093 URL: https://issues.jboss.org/browse/ISPN-2093 Project: Infinispan Issue Type: Bug Components: State transfer Affects Versions: 5.1.5.FINAL Reporter: Michal Linhard Assignee: Manik Surtani The symptoms are basically the same as in previous issue: ISPN-1838 but I didn't want to mix with the old comments in case the cause here is different. happened in 32 node elasticity test http://www.qa.jboss.com/~mlinhard/hyperion/run148-elas-dist-32-ER11/logs/... We start with 16 nodes and add up to 31 nodes when we add the 32nd node the state transfer takes 580sec. previously all state transfers took under 2min. -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] (ISPN-2260) Cache manager shutdown blocks for 1 minute if the JGroups channel has already been stopped

by Dan Berindei (JIRA)

Dan Berindei created ISPN-2260: ---------------------------------- Summary: Cache manager shutdown blocks for 1 minute if the JGroups channel has already been stopped Key: ISPN-2260 URL: https://issues.jboss.org/browse/ISPN-2260 Project: Infinispan Issue Type: Bug Components: Locking and Concurrency Affects Versions: 5.1.6.FINAL Reporter: Dan Berindei Assignee: Dan Berindei Priority: Critical Fix For: 5.1.7.Final When the JGroups channel is not created by Infinispan, as it happens in AS7, the channel can be closed before the cache manager has finished stopping. Because of JGRP-1508, this can block cache leave commands (or cache view installation commands, if the local node was the coordinator) for 1 minute (the default RSVP timeout). We can work around this, at least for cache view installation commands, by calling shutdownNow() on the cache view installation executor. -- 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, 7 months

2
5
0 / 0

[JBoss JIRA] (ISPN-2114) MinViewIdCalculusTest.testMinViewId1 randomly failing

by Galder Zamarreño (JIRA)

11 years, 7 months

4
15
0 / 0

[JBoss JIRA] (ISPN-2312) TransactionTable does not compute minViewId correctly after NBST was introduced

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-2312: ----------------------------------- Summary: TransactionTable does not compute minViewId correctly after NBST was introduced Key: ISPN-2312 URL: https://issues.jboss.org/browse/ISPN-2312 Project: Infinispan Issue Type: Bug Components: State transfer, Transactions Affects Versions: 5.2.0.Alpha3 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 5.2.0.Alpha4 This happens for transactions that arrive via state transfer. The view id of these transactions is currently wrong - it should be the view id in which they were created instead of the current view id at the time they were transferred. TransactionTable.lockKeyAndCheckOwnership relies on this and consequently does not work correctly for transferred transactions. Also TransactionTable listens for JGroup view changes instead of CacheTopology updates. This is another reason minViewId calculation is wrong. -- 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, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (ISPN-863) Eviction based on JVM memory utilization

by Dave Marion (JIRA)

Eviction based on JVM memory utilization ---------------------------------------- Key: ISPN-863 URL: https://issues.jboss.org/browse/ISPN-863 Project: Infinispan Issue Type: Enhancement Components: Eviction Affects Versions: 4.2.0.Final Environment: N/A Reporter: Dave Marion Assignee: Manik Surtani Allow user to specify percentage threshold upon which eviction will kick in and begin evicting entries based on the specified strategy. This would allow user to create a cache that will attempt to keep as many entries in memory as possible without having to specify maxEntries. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

8
38
0 / 0

[JBoss JIRA] (ISPN-2325) Fix JMX issues introduced by automatic MBean registration

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2325: -------------------------------------- Summary: Fix JMX issues introduced by automatic MBean registration Key: ISPN-2325 URL: https://issues.jboss.org/browse/ISPN-2325 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 5.2.0.Alpha4 Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.Beta1 The grand majority of failures in https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/827 are result of ISPN-2290. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] (ISPN-2303) GroupsChFunctionalTest.testRehash fails randomly

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2303: -------------------------------------- Summary: GroupsChFunctionalTest.testRehash fails randomly Key: ISPN-2303 URL: https://issues.jboss.org/browse/ISPN-2303 Project: Infinispan Issue Type: Bug Components: Distributed Cache Reporter: Galder Zamarreño Assignee: Adrian Nistor Fix For: 5.2.0.Alpha4 Fails with: {code} testRehash(org.infinispan.distribution.groups.GroupsChFunctionalTest): 2{code} I'll put a link for the TRACE logs. @Adrian, assigning it to you since it's distribution related. -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] (ISPN-2329) TableManipulation.getDatabasetype does not release used connections

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2329: ---------------------------------- Summary: TableManipulation.getDatabasetype does not release used connections Key: ISPN-2329 URL: https://issues.jboss.org/browse/ISPN-2329 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 5.2.0.Alpha4 Reporter: Thomas Fromm Assignee: Tristan Tarrant Priority: Critical TableManipulation.getDatabasetype does not release used connections for data type determination. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] (ISPN-2204) MapReduceTask without Reducer

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2204: ---------------------------------- Summary: MapReduceTask without Reducer Key: ISPN-2204 URL: https://issues.jboss.org/browse/ISPN-2204 Project: Infinispan Issue Type: Feature Request Components: Core API Affects Versions: 5.1.5.FINAL Reporter: Thomas Fromm Assignee: Manik Surtani Definition of Reducer should be optional. Workaround is to set dummy reducer. -- 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, 7 months

2
8
0 / 0

[JBoss JIRA] (ISPN-2317) Distributed Callable with automatic filled keys in environment where current node = owner

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2317: ---------------------------------- Summary: Distributed Callable with automatic filled keys in environment where current node = owner Key: ISPN-2317 URL: https://issues.jboss.org/browse/ISPN-2317 Project: Infinispan Issue Type: Feature Request Components: Distributed Execution and Map/Reduce Affects Versions: 5.1.7.Final Reporter: Thomas Fromm Assignee: Vladimir Blagojevic In a distributed cache I need to process every key one time. My solution is ATM to create a distributed call and on every node walk through the keyset of the cache and process every node, where the current node is the owner. This solution works, but is not really nice. I'd like to have a specific Distributed callable for this or an flag/option to enable that the keys where the current node is owner are used at setEnvironment(...). -- 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, 7 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2012