January 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2318) Reimplement a Topology-Aware Consistent Hash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2318?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2318: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 868832|https://bugzilla.redhat.com/show_bug.cgi?id=868832] from ASSIGNED to CLOSED > Reimplement a Topology-Aware Consistent Hash > -------------------------------------------- > > Key: ISPN-2318 > URL: https://issues.jboss.org/browse/ISPN-2318 > Project: Infinispan > Issue Type: Task > Components: Core API, Distributed Cache > Affects Versions: 5.2.0.Alpha3 > Reporter: Erik Salter > Assignee: Dan Berindei > Priority: Blocker > Fix For: 5.2.0.Beta3 > > > Even with the advent of x-site replication, the TACH is useful to stripe key ownership across machines and/or racks for resiliency. This feature should be refactored from the 5.1 impl. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2703) The "machine" attribute of server hinting does not work

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2703?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-2703. -------------------------------- Resolution: Won't Fix I'm rejecting the bug, as this is expected when numSegments==1. Martin, thanks for the explanation on the build system, I'll try to use it on the next JDG-related bug :) > The "machine" attribute of server hinting does not work > ------------------------------------------------------- > > Key: ISPN-2703 > URL: https://issues.jboss.org/browse/ISPN-2703 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.Beta6 > Reporter: Martin Gencur > Assignee: Dan Berindei > Priority: Critical > Fix For: 5.2.0.Final > > Attachments: server-hinting-logs.zip, trace_log_machine_attribute_failing.txt > > > The rack and site attributes already work correctly. I'm creating this one issue just for the remaining "machine" attribute. > Will attach trace logs -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2703) The "machine" attribute of server hinting does not work

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2703?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-2703: ------------------------------------ Ah, sorry, I looked at the test's infinispan.xml but I didn't notice numSegments was set to 1. Yes, this is expected (but perhaps under-documented). The consistent hash doesn't actually distribute keys among the nodes, it only distributes segments. Each key is mapped to a segment, and the segment is mapped to a list of owners. So if there is only one segment, all the keys will map to that segment, and all of them will have the same owners. > The "machine" attribute of server hinting does not work > ------------------------------------------------------- > > Key: ISPN-2703 > URL: https://issues.jboss.org/browse/ISPN-2703 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.Beta6 > Reporter: Martin Gencur > Assignee: Dan Berindei > Priority: Critical > Fix For: 5.2.0.Final > > Attachments: server-hinting-logs.zip, trace_log_machine_attribute_failing.txt > > > The rack and site attributes already work correctly. I'm creating this one issue just for the remaining "machine" attribute. > Will attach trace logs -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2740) NPE at AbstractEnlistmentAdapter

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2740?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2740: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/1593 > NPE at AbstractEnlistmentAdapter > -------------------------------- > > Key: ISPN-2740 > URL: https://issues.jboss.org/browse/ISPN-2740 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 5.2.0.CR2 > Reporter: Thomas Fromm > Assignee: Adrian Nistor > Fix For: 5.2.0.Final > > > Happens on local cache with pessimistic tx. > ERROR 22.01.13 17:21:31,510 [IS-dev-blade-Node-1-MThread-1] DummyTransaction ISPN000111: afterCompletion() failed for SynchronizationAdapter{localTransaction=LocalTransaction{remoteLockedNodes=null, isMarkedForRollback=false, lockedKeys=null, backupKeyLocks=null, topologyId=-1, isFromStateTransfer=false} org.infinispan.transaction.synchronization.SyncLocalTransaction@fb} org.infinispan.transaction.synchronization.SynchronizationAdapter@11a > java.lang.NullPointerException > at org.infinispan.transaction.AbstractEnlistmentAdapter.mayHaveRemoteLocks(AbstractEnlistmentAdapter.java:96) > at org.infinispan.transaction.AbstractEnlistmentAdapter.removeTransactionInfoRemotely(AbstractEnlistmentAdapter.java:86) > at org.infinispan.transaction.AbstractEnlistmentAdapter.releaseLocksForCompletedTransaction(AbstractEnlistmentAdapter.java:82) > at org.infinispan.transaction.synchronization.SynchronizationAdapter.afterCompletion(SynchronizationAdapter.java:85) > at org.infinispan.transaction.tm.DummyTransaction.notifyAfterCompletion(DummyTransaction.java:285) > at org.infinispan.transaction.tm.DummyTransaction.runCommitTx(DummyTransaction.java:334) > at org.infinispan.transaction.tm.DummyTransaction.commit(DummyTransaction.java:91) > at org.infinispan.transaction.tm.DummyBaseTransactionManager.commit(DummyBaseTransactionManager.java:102) > ... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node crash

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Michal Linhard commented on ISPN-2632: -------------------------------------- in resilience test 32-28-32 (numowners5) the unevenness is from the beginning of test (I don't think this needs a different JIRA, or does it ?) http://www.qa.jboss.com/~mlinhard/hyperion3/run0035-resi-32-28-32-ER9/rep... > Uneven request balancing after node crash > ----------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR1, 5.2.0.CR2 > Reporter: Michal Linhard > Assignee: Dan Berindei > Priority: Blocker > Fix For: 5.2.0.CR2, 5.2.0.Final > > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2738) Joining node ignored by hotrod clients in REPL clustering mode

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2738?page=com.atlassian.jira.plugin.... ] Work on ISPN-2738 started by Galder Zamarreño. > Joining node ignored by hotrod clients in REPL clustering mode > -------------------------------------------------------------- > > Key: ISPN-2738 > URL: https://issues.jboss.org/browse/ISPN-2738 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.CR2 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Fix For: 5.2.0.Final > > > resilience 4-3-4 REPL mode for JDG 6.1.0.ER9 (infinispan 5.2.0.CR2): > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... > after rejoin of killed node the load is not redistributed to all three nodes again -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2715) org.infinispan.distexec.mapreduce.TopologyAwareTwoNodesMapReduceTest.testCombinerDoesNotChangeResult test fails randomly

by Anna Manukyan (JIRA)

[ https://issues.jboss.org/browse/ISPN-2715?page=com.atlassian.jira.plugin.... ] Anna Manukyan updated ISPN-2715: -------------------------------- Assignee: Anna Manukyan (was: Vladimir Blagojevic) > org.infinispan.distexec.mapreduce.TopologyAwareTwoNodesMapReduceTest.testCombinerDoesNotChangeResult test fails randomly > ------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-2715 > URL: https://issues.jboss.org/browse/ISPN-2715 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.0.CR1 > Reporter: Anna Manukyan > Assignee: Anna Manukyan > Labels: testsuite_stability > Attachments: testCombinerDoesNotChangeResult-0.tgz > > > org.infinispan.distexec.mapreduce.TopologyAwareTwoNodesMapReduceTest.testCombinerDoesNotChangeResult test fails randomly on all environments. The failure error is: > {code} > java.lang.AssertionError > at org.infinispan.distexec.mapreduce.BaseWordCountMapReduceTest.testCombinerDoesNotChangeResult(BaseWordCountMapReduceTest.java:217) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > {code} -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node crash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2632: ----------------------------------------------- Michal Linhard <mlinhard(a)redhat.com> changed the Status of [bug 886549|https://bugzilla.redhat.com/show_bug.cgi?id=886549] from ON_QA to ASSIGNED > Uneven request balancing after node crash > ----------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR1, 5.2.0.CR2 > Reporter: Michal Linhard > Assignee: Dan Berindei > Priority: Blocker > Fix For: 5.2.0.CR2, 5.2.0.Final > > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node crash

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Michal Linhard reopened ISPN-2632: ---------------------------------- This appeared again in JDG 6.1.0.ER9 tests (infinispan 5.2.0.CR2) http://www.qa.jboss.com/~mlinhard/hyperion3/run0034-resi-8-6-8-ER9/report... > Uneven request balancing after node crash > ----------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR1 > Reporter: Michal Linhard > Assignee: Dan Berindei > Priority: Blocker > Fix For: 5.2.0.CR2, 5.2.0.Final > > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node crash

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Michal Linhard updated ISPN-2632: --------------------------------- Affects Version/s: 5.2.0.CR2 > Uneven request balancing after node crash > ----------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR1, 5.2.0.CR2 > Reporter: Michal Linhard > Assignee: Dan Berindei > Priority: Blocker > Fix For: 5.2.0.CR2, 5.2.0.Final > > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- 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, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2013