[JBoss JIRA] (ISPN-4843) org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations fails randomly
by Vojtech Juranek (JIRA)
[ https://issues.jboss.org/browse/ISPN-4843?page=com.atlassian.jira.plugin.... ]
Vojtech Juranek updated ISPN-4843:
----------------------------------
Affects Version/s: 7.0.0.Final
> org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations fails randomly
> ---------------------------------------------------------------------------------------------------
>
> Key: ISPN-4843
> URL: https://issues.jboss.org/browse/ISPN-4843
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 7.0.0.Final, 5.2.10.Final
> Reporter: Michal Vinkler
> Labels: 5.2.x, testsuite_stability
>
> org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations fails, so far, I've seen it on Windows (seems random there) and on RHEL7 (seems consistent - every JDK).
> Error Message
> {code}
> Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete() throws java.lang.InterruptedException on object of type StateTransferManagerImpl
> Stacktrace
> org.infinispan.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete() throws java.lang.InterruptedException on object of type StateTransferManagerImpl
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:205)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:886)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:657)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:646)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:549)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:217)
> at org.infinispan.CacheImpl.start(CacheImpl.java:582)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:686)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:649)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:545)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:518)
> at org.infinispan.manager.CacheManagerTest$4$1.call(CacheManagerTest.java:374)
> at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1237)
> at org.infinispan.manager.CacheManagerTest$4.call(CacheManagerTest.java:370)
> at org.infinispan.test.TestingUtil.withCacheManagers(TestingUtil.java:1252)
> at org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations(CacheManagerTest.java:356)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.infinispan.CacheException: Initial state transfer timed out for cache ___defaultcache on CacheManagerTest-NodeA-49570
> at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:216)
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:203)
> ... 36 more
> ... Removed 19 stack frames
> {code}
> Unrelated to https://issues.jboss.org/browse/ISPN-3963.
> Jenkins job link:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-manu-infinisp...
> Downstream BZ was: https://bugzilla.redhat.com/show_bug.cgi?id=1102058
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-4843) org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations fails randomly
by Vojtech Juranek (JIRA)
[ https://issues.jboss.org/browse/ISPN-4843?page=com.atlassian.jira.plugin.... ]
Vojtech Juranek updated ISPN-4843:
----------------------------------
Labels: 5.2.x testsuite_stability (was: 5.2.x)
> org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations fails randomly
> ---------------------------------------------------------------------------------------------------
>
> Key: ISPN-4843
> URL: https://issues.jboss.org/browse/ISPN-4843
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 5.2.10.Final
> Reporter: Michal Vinkler
> Labels: 5.2.x, testsuite_stability
>
> org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations fails, so far, I've seen it on Windows (seems random there) and on RHEL7 (seems consistent - every JDK).
> Error Message
> {code}
> Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete() throws java.lang.InterruptedException on object of type StateTransferManagerImpl
> Stacktrace
> org.infinispan.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete() throws java.lang.InterruptedException on object of type StateTransferManagerImpl
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:205)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:886)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:657)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:646)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:549)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:217)
> at org.infinispan.CacheImpl.start(CacheImpl.java:582)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:686)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:649)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:545)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:518)
> at org.infinispan.manager.CacheManagerTest$4$1.call(CacheManagerTest.java:374)
> at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1237)
> at org.infinispan.manager.CacheManagerTest$4.call(CacheManagerTest.java:370)
> at org.infinispan.test.TestingUtil.withCacheManagers(TestingUtil.java:1252)
> at org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations(CacheManagerTest.java:356)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.infinispan.CacheException: Initial state transfer timed out for cache ___defaultcache on CacheManagerTest-NodeA-49570
> at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:216)
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:203)
> ... 36 more
> ... Removed 19 stack frames
> {code}
> Unrelated to https://issues.jboss.org/browse/ISPN-3963.
> Jenkins job link:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-manu-infinisp...
> Downstream BZ was: https://bugzilla.redhat.com/show_bug.cgi?id=1102058
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-4843) org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations fails randomly
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4843?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-4843:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1102058, https://bugzilla.redhat.com/show_bug.cgi?id=1138572, https://bugzilla.redhat.com/show_bug.cgi?id=1172093 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1102058, https://bugzilla.redhat.com/show_bug.cgi?id=1138572)
> org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations fails randomly
> ---------------------------------------------------------------------------------------------------
>
> Key: ISPN-4843
> URL: https://issues.jboss.org/browse/ISPN-4843
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 5.2.10.Final
> Reporter: Michal Vinkler
> Labels: 5.2.x, testsuite_stability
>
> org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations fails, so far, I've seen it on Windows (seems random there) and on RHEL7 (seems consistent - every JDK).
> Error Message
> {code}
> Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete() throws java.lang.InterruptedException on object of type StateTransferManagerImpl
> Stacktrace
> org.infinispan.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete() throws java.lang.InterruptedException on object of type StateTransferManagerImpl
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:205)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:886)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:657)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:646)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:549)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:217)
> at org.infinispan.CacheImpl.start(CacheImpl.java:582)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:686)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:649)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:545)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:518)
> at org.infinispan.manager.CacheManagerTest$4$1.call(CacheManagerTest.java:374)
> at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1237)
> at org.infinispan.manager.CacheManagerTest$4.call(CacheManagerTest.java:370)
> at org.infinispan.test.TestingUtil.withCacheManagers(TestingUtil.java:1252)
> at org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations(CacheManagerTest.java:356)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.infinispan.CacheException: Initial state transfer timed out for cache ___defaultcache on CacheManagerTest-NodeA-49570
> at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:216)
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:203)
> ... 36 more
> ... Removed 19 stack frames
> {code}
> Unrelated to https://issues.jboss.org/browse/ISPN-3963.
> Jenkins job link:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-manu-infinisp...
> Downstream BZ was: https://bugzilla.redhat.com/show_bug.cgi?id=1102058
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5046) PartitionHandling: split during commit can leave the cache inconsistent after merge
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/ISPN-5046?page=com.atlassian.jira.plugin.... ]
Bela Ban edited comment on ISPN-5046 at 12/9/14 5:41 AM:
---------------------------------------------------------
What if A and B crashed instead of getting partitioned away ?
* How long will C hang on to T trying to contact B to see if B committed T ?
* What if E joined CD to form CDE ?
** At this point, CDE would not be degraded any longer and might copy key K from the new primary owner B to E
Or what happens if there *was* a partition, so we now have AB and CD, but now X joins AB into ABX and Y joined CD into CDY ?
NOTE: my comments on new nodes joining a partition are probably moot, as I assume that your model precludes this; and there is always a static set of nodes to work with.. ?
was (Author: belaban):
What if A and B crashed instead of getting partitioned away ?
* How long will C hang on to T trying to contact B to see if B committed T ?
* What if E joined CD to form CDE ?
** At this point, CDE would not be degraded any longer and might copy key K from the new primary owner B to E
Or what happens if there *was* a partition, so we now have AB and CD, but now X joins AB into ABX and Y joined CD into CDY ?
> PartitionHandling: split during commit can leave the cache inconsistent after merge
> -----------------------------------------------------------------------------------
>
> Key: ISPN-5046
> URL: https://issues.jboss.org/browse/ISPN-5046
> Project: Infinispan
> Issue Type: Bug
> Components: Core, State Transfer
> Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
> Reporter: Dan Berindei
> Priority: Critical
> Fix For: 7.1.0.Beta1
>
>
> Say we have a cluster ABCD; a transaction T was started on A, with B as the primary owner and C the backup owner. B and C both acknowledge the prepare, and the network splits into AB and CD right before A sends the commit command. Eventually A suspects C and D, but the commit still succeeds on B before C and D are suspected. And SuspectExceptions are ignored for commit commands, so the user won't see any error.
> However, C will eventually suspect A and B. When the CD cache topology is installed, it will roll back transaction T. After the merge, both partitions are in degraded mode, so we assume that they both have the latest data and the key is never updated on C.
> From C's point of view, this is very similar to ISPN-3421. The fix should also be similar, we could delay the transaction rollback on C until we get a confirmation from B that T was not committed there. Since B is inaccessible, it will eventually get a SuspectException and the CD cache topology, at which point the cache is in degraded mode and it can wait for a merge. On merge, it should check the status of the transaction on B again, and either commit or rollback based on what B did.
> We also need to suspend the cleanup of completed transactions while the cache is in degraded mode, otherwise C might not find T on B after the merge.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5046) PartitionHandling: split during commit can leave the cache inconsistent after merge
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/ISPN-5046?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on ISPN-5046:
--------------------------------
What if A and B crashed instead of getting partitioned away ?
* How long will C hang on to T trying to contact B to see if B committed T ?
* What if E joined CD to form CDE ?
** At this point, CDE would not be degraded any longer and might copy key K from the new primary owner B to E
Or what happens if there *was* a partition, so we now have AB and CD, but now X joins AB into ABX and Y joined CD into CDY ?
> PartitionHandling: split during commit can leave the cache inconsistent after merge
> -----------------------------------------------------------------------------------
>
> Key: ISPN-5046
> URL: https://issues.jboss.org/browse/ISPN-5046
> Project: Infinispan
> Issue Type: Bug
> Components: Core, State Transfer
> Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
> Reporter: Dan Berindei
> Priority: Critical
> Fix For: 7.1.0.Beta1
>
>
> Say we have a cluster ABCD; a transaction T was started on A, with B as the primary owner and C the backup owner. B and C both acknowledge the prepare, and the network splits into AB and CD right before A sends the commit command. Eventually A suspects C and D, but the commit still succeeds on B before C and D are suspected. And SuspectExceptions are ignored for commit commands, so the user won't see any error.
> However, C will eventually suspect A and B. When the CD cache topology is installed, it will roll back transaction T. After the merge, both partitions are in degraded mode, so we assume that they both have the latest data and the key is never updated on C.
> From C's point of view, this is very similar to ISPN-3421. The fix should also be similar, we could delay the transaction rollback on C until we get a confirmation from B that T was not committed there. Since B is inaccessible, it will eventually get a SuspectException and the CD cache topology, at which point the cache is in degraded mode and it can wait for a merge. On merge, it should check the status of the transaction on B again, and either commit or rollback based on what B did.
> We also need to suspend the cleanup of completed transactions while the cache is in degraded mode, otherwise C might not find T on B after the merge.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5062) Cross site state transfer - incorrect status of push operation
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5062?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-5062:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1172034
> Cross site state transfer - incorrect status of push operation
> ---------------------------------------------------------------
>
> Key: ISPN-5062
> URL: https://issues.jboss.org/browse/ISPN-5062
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 7.1.0.Alpha1
> Reporter: Matej Čimbora
> Assignee: Pedro Ruivo
>
> Status of push operation remains at value "CANCELLED" after the push operation was cancelled and reinvoked (even if state transfer is currently in progress) - "SENDING" value is expected. Otherwise works as expected (after the state transfer completes, status is switched to "OK").
> - Sites LON (lonCache) - main, BRN (brnCache) - backup
> Consider the following scenario:
> [standalone@localhost:9999 distributed-cache=lonCache] site --push BRN
> ok
> [standalone@localhost:9999 distributed-cache=lonCache] site --cancelpush BRN
> ok
> [standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
> BRN=CANCELED
> [standalone@localhost:9999 distributed-cache=lonCache] site --push BRN
> ok
> [standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
> BRN=CANCELED
> [standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
> BRN=OK
> Expected behavior:
> [standalone@localhost:9999 distributed-cache=lonCache] site --push BRN
> ok
> [standalone@localhost:9999 distributed-cache=lonCache] site --cancelpush BRN
> ok
> [standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
> BRN=CANCELED
> [standalone@localhost:9999 distributed-cache=lonCache] site --push BRN
> ok
> [standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
> BRN=SENDING
> [standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
> BRN=OK
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5062) Cross site state transfer - incorrect status of push operation
by Matej Čimbora (JIRA)
Matej Čimbora created ISPN-5062:
-----------------------------------
Summary: Cross site state transfer - incorrect status of push operation
Key: ISPN-5062
URL: https://issues.jboss.org/browse/ISPN-5062
Project: Infinispan
Issue Type: Bug
Components: State Transfer
Affects Versions: 7.1.0.Alpha1
Reporter: Matej Čimbora
Assignee: Pedro Ruivo
Status of push operation remains at value "CANCELLED" after the push operation was cancelled and reinvoked (even if state transfer is currently in progress) - "SENDING" value is expected. Otherwise works as expected (after the state transfer completes, status is switched to "OK").
- Sites LON (lonCache) - main, BRN (brnCache) - backup
Consider the following scenario:
[standalone@localhost:9999 distributed-cache=lonCache] site --push BRN
ok
[standalone@localhost:9999 distributed-cache=lonCache] site --cancelpush BRN
ok
[standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
BRN=CANCELED
[standalone@localhost:9999 distributed-cache=lonCache] site --push BRN
ok
[standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
BRN=CANCELED
[standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
BRN=OK
Expected behavior:
[standalone@localhost:9999 distributed-cache=lonCache] site --push BRN
ok
[standalone@localhost:9999 distributed-cache=lonCache] site --cancelpush BRN
ok
[standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
BRN=CANCELED
[standalone@localhost:9999 distributed-cache=lonCache] site --push BRN
ok
[standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
BRN=SENDING
[standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
BRN=OK
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5061) Cross site state transfer - NPE on consumer site when backup cache is not present
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5061?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-5061:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1172021
> Cross site state transfer - NPE on consumer site when backup cache is not present
> ---------------------------------------------------------------------------------
>
> Key: ISPN-5061
> URL: https://issues.jboss.org/browse/ISPN-5061
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 7.1.0.Alpha1
> Reporter: Matej Čimbora
> Assignee: Pedro Ruivo
>
> NPE detected on consumer site after invoking push operation on producer site. Occurs when corresponding cache does not exist on consumer site (either with the same name as the main cache or specified via <backup-for> option).
> Configuration:
> 2 sites, BRN (main), LON (backup)
> Producer site CLI:
> Unable to pushState to 'LON'. org.infinispan.commons.CacheException: Problems invoking command.
> Consumer site log:
> 11:18:45,245 WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (remote-thread--p3-t1) ISPN000071: Caught exception when handling command XSiteStateTransferControlCommand{control=START_RECEIVE, siteName='LON', statusOk=false, cacheName='lonCache'}: java.lang.NullPointerException
> at org.infinispan.xsite.BackupReceiverImpl.invokeRemotelyInLocalSite(BackupReceiverImpl.java:213) [infinispan-core.jar:7.1.0.Alpha1]
> at org.infinispan.xsite.BackupReceiverImpl.handleStateTransferControl(BackupReceiverImpl.java:90) [infinispan-core.jar:7.1.0.Alpha1]
> at org.infinispan.xsite.statetransfer.XSiteStateTransferControlCommand.performInLocalSite(XSiteStateTransferControlCommand.java:41) [infinispan-core.jar:7.1.0.Alpha1]
> at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher$3.run(CommandAwareRpcDispatcher.java:252) [infinispan-core.jar:7.1.0.Alpha1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60]
> 11:18:45,420 WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (remote-thread--p3-t1) ISPN000071: Caught exception when handling command XSiteStateTransferControlCommand{control=FINISH_RECEIVE, siteName='LON', statusOk=false, cacheName='lonCache'}: java.lang.NullPointerException
> at org.infinispan.xsite.BackupReceiverImpl.invokeRemotelyInLocalSite(BackupReceiverImpl.java:213) [infinispan-core.jar:7.1.0.Alpha1]
> at org.infinispan.xsite.BackupReceiverImpl.handleStateTransferControl(BackupReceiverImpl.java:90) [infinispan-core.jar:7.1.0.Alpha1]
> at org.infinispan.xsite.statetransfer.XSiteStateTransferControlCommand.performInLocalSite(XSiteStateTransferControlCommand.java:41) [infinispan-core.jar:7.1.0.Alpha1]
> at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher$3.run(CommandAwareRpcDispatcher.java:252) [infinispan-core.jar:7.1.0.Alpha1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60]
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5061) Cross site state transfer - NPE on consumer site when backup cache is not present
by Matej Čimbora (JIRA)
Matej Čimbora created ISPN-5061:
-----------------------------------
Summary: Cross site state transfer - NPE on consumer site when backup cache is not present
Key: ISPN-5061
URL: https://issues.jboss.org/browse/ISPN-5061
Project: Infinispan
Issue Type: Bug
Components: State Transfer
Affects Versions: 7.1.0.Alpha1
Reporter: Matej Čimbora
Assignee: Pedro Ruivo
NPE detected on consumer site after invoking push operation on producer site. Occurs when corresponding cache does not exist on consumer site (either with the same name as the main cache or specified via <backup-for> option).
Configuration:
2 sites, BRN (main), LON (backup)
Producer site CLI:
Unable to pushState to 'LON'. org.infinispan.commons.CacheException: Problems invoking command.
Consumer site log:
11:18:45,245 WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (remote-thread--p3-t1) ISPN000071: Caught exception when handling command XSiteStateTransferControlCommand{control=START_RECEIVE, siteName='LON', statusOk=false, cacheName='lonCache'}: java.lang.NullPointerException
at org.infinispan.xsite.BackupReceiverImpl.invokeRemotelyInLocalSite(BackupReceiverImpl.java:213) [infinispan-core.jar:7.1.0.Alpha1]
at org.infinispan.xsite.BackupReceiverImpl.handleStateTransferControl(BackupReceiverImpl.java:90) [infinispan-core.jar:7.1.0.Alpha1]
at org.infinispan.xsite.statetransfer.XSiteStateTransferControlCommand.performInLocalSite(XSiteStateTransferControlCommand.java:41) [infinispan-core.jar:7.1.0.Alpha1]
at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher$3.run(CommandAwareRpcDispatcher.java:252) [infinispan-core.jar:7.1.0.Alpha1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60]
11:18:45,420 WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (remote-thread--p3-t1) ISPN000071: Caught exception when handling command XSiteStateTransferControlCommand{control=FINISH_RECEIVE, siteName='LON', statusOk=false, cacheName='lonCache'}: java.lang.NullPointerException
at org.infinispan.xsite.BackupReceiverImpl.invokeRemotelyInLocalSite(BackupReceiverImpl.java:213) [infinispan-core.jar:7.1.0.Alpha1]
at org.infinispan.xsite.BackupReceiverImpl.handleStateTransferControl(BackupReceiverImpl.java:90) [infinispan-core.jar:7.1.0.Alpha1]
at org.infinispan.xsite.statetransfer.XSiteStateTransferControlCommand.performInLocalSite(XSiteStateTransferControlCommand.java:41) [infinispan-core.jar:7.1.0.Alpha1]
at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher$3.run(CommandAwareRpcDispatcher.java:252) [infinispan-core.jar:7.1.0.Alpha1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60]
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5021) Nodes that finish the rebalance later can see outdated values
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5021?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5021:
-----------------------------------------------
Radim Vansa <rvansa(a)redhat.com> changed the Status of [bug 1163665|https://bugzilla.redhat.com/show_bug.cgi?id=1163665] from ON_QA to ASSIGNED
> Nodes that finish the rebalance later can see outdated values
> -------------------------------------------------------------
>
> Key: ISPN-5021
> URL: https://issues.jboss.org/browse/ISPN-5021
> Project: Infinispan
> Issue Type: Bug
> Components: Core, State Transfer
> Affects Versions: 7.0.2.Final
> Reporter: Dan Berindei
> Assignee: Pedro Ruivo
> Priority: Critical
> Fix For: 7.1.0.Beta1
>
>
> Copied from [ISPN-4444|https://issues.jboss.org/browse/ISPN-4444?focusedCommentId=1302...]
> If the CH_UPDATE command is delayed on the old owner, the new owners might update the key without the old owner knowing, and a locality check on the old owner won't help.
> I remember one thing that struck me when reading the Raft algorithm was that they install configuration changes symmetrically, in 3 phases. We might need to do the same for our rebalance: start a rebalance with read_ch=old, write_ch=old+new, when the new owners have all the data install read_ch=new, write_ch=old+new, and finally read_ch=new, write_ch=new. Old cache entries are removed during the 2nd topology update, and further writes should be ignored, in order for this to work.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months