[JBoss JIRA] (ISPN-5889) Merge views not dealt with in Hot Rod server
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-5889?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-5889:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Merge views not dealt with in Hot Rod server
> --------------------------------------------
>
> Key: ISPN-5889
> URL: https://issues.jboss.org/browse/ISPN-5889
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 8.0.1.Final, 8.1.0.Alpha2
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 8.1.0.Beta2, 8.1.0.Final
>
>
> Hot Rod server does not deal with merge views, so when members return back to the cluster, the view is not updated. The Hot Rod server view change listener currently only deals with nodes leaving or crashing. This problem is not a big one since it just means that until the next view change happens, clients will work with a reduced view, working in a suboptimal way, but it won't have correctness impact.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5895) RebalancePolicyJmxTest.testJoinAndLeaveWithRebalanceSuspendedAwaitingInitialTransfer random failures
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5895?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-5895:
-------------------------------
Status: Pull Request Sent (was: Reopened)
> RebalancePolicyJmxTest.testJoinAndLeaveWithRebalanceSuspendedAwaitingInitialTransfer random failures
> ----------------------------------------------------------------------------------------------------
>
> Key: ISPN-5895
> URL: https://issues.jboss.org/browse/ISPN-5895
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite - Core
> Affects Versions: 8.1.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Blocker
> Labels: testsuite_stability
> Fix For: 8.1.0.Beta1
>
>
> The test sometimes fails because the rebalance finishes too quickly after it is enabled.
> {noformat}
> 17:22:35,605 DEBUG (testng-RebalancePolicyJmxTest:[]) [RebalancePolicyJmxTest] Rebalancing with nodes NodeI-11719 NodeJ-4803 NodeK-58683 NodeL-10033
> 17:22:35,621 INFO (remote-thread-NodeI-p45498-t6:[]) [CLUSTER] ISPN000310: Starting cluster-wide rebalance for cache ___defaultcache, topology CacheTopology{id=3, rebalanceId=2, currentCH=DefaultConsistentHash{ns=60, owners = (2)[NodeI-11719: 30+30, NodeJ-4803: 30+30]}, pendingCH=DefaultConsistentHash{ns=60, owners = (4)[NodeI-11719: 15+15, NodeJ-4803: 15+15, NodeK-58683: 15+15, NodeL-10033: 15+15]}, unionCH=null, actualMembers=[NodeI-11719, NodeJ-4803, NodeK-58683, NodeL-10033]}
> 17:22:35,643 INFO (remote-thread-NodeI-p45498-t6:[]) [CLUSTER] ISPN000336: Finished cluster-wide rebalance for cache ___defaultcache, topology id = 3
> 17:22:37,630 ERROR (testng-RebalancePolicyJmxTest:[]) [UnitTestTestNGListener] Test testJoinAndLeaveWithRebalanceSuspended(org.infinispan.statetransfer.RebalancePolicyJmxTest) failed.
> java.lang.AssertionError: expected:<IN_PROGRESS> but was:<COMPLETE>
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:101) ~[testng-6.8.8.jar:?]
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:108) ~[testng-6.8.8.jar:?]
> at org.infinispan.statetransfer.RebalancePolicyJmxTest.doTest(RebalancePolicyJmxTest.java:111) ~[test-classes/:?]
> at org.infinispan.statetransfer.RebalancePolicyJmxTest.testJoinAndLeaveWithRebalanceSuspended(RebalancePolicyJmxTest.java:36) ~[test-classes/:?]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5895) RebalancePolicyJmxTest.testJoinAndLeaveWithRebalanceSuspendedAwaitingInitialTransfer random failures
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5895?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-5895:
-------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/3788, https://github.com/infinispan/infinispan/pull/3822 (was: https://github.com/infinispan/infinispan/pull/3788)
> RebalancePolicyJmxTest.testJoinAndLeaveWithRebalanceSuspendedAwaitingInitialTransfer random failures
> ----------------------------------------------------------------------------------------------------
>
> Key: ISPN-5895
> URL: https://issues.jboss.org/browse/ISPN-5895
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite - Core
> Affects Versions: 8.1.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Blocker
> Labels: testsuite_stability
> Fix For: 8.1.0.Beta1
>
>
> The test sometimes fails because the rebalance finishes too quickly after it is enabled.
> {noformat}
> 17:22:35,605 DEBUG (testng-RebalancePolicyJmxTest:[]) [RebalancePolicyJmxTest] Rebalancing with nodes NodeI-11719 NodeJ-4803 NodeK-58683 NodeL-10033
> 17:22:35,621 INFO (remote-thread-NodeI-p45498-t6:[]) [CLUSTER] ISPN000310: Starting cluster-wide rebalance for cache ___defaultcache, topology CacheTopology{id=3, rebalanceId=2, currentCH=DefaultConsistentHash{ns=60, owners = (2)[NodeI-11719: 30+30, NodeJ-4803: 30+30]}, pendingCH=DefaultConsistentHash{ns=60, owners = (4)[NodeI-11719: 15+15, NodeJ-4803: 15+15, NodeK-58683: 15+15, NodeL-10033: 15+15]}, unionCH=null, actualMembers=[NodeI-11719, NodeJ-4803, NodeK-58683, NodeL-10033]}
> 17:22:35,643 INFO (remote-thread-NodeI-p45498-t6:[]) [CLUSTER] ISPN000336: Finished cluster-wide rebalance for cache ___defaultcache, topology id = 3
> 17:22:37,630 ERROR (testng-RebalancePolicyJmxTest:[]) [UnitTestTestNGListener] Test testJoinAndLeaveWithRebalanceSuspended(org.infinispan.statetransfer.RebalancePolicyJmxTest) failed.
> java.lang.AssertionError: expected:<IN_PROGRESS> but was:<COMPLETE>
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:101) ~[testng-6.8.8.jar:?]
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:108) ~[testng-6.8.8.jar:?]
> at org.infinispan.statetransfer.RebalancePolicyJmxTest.doTest(RebalancePolicyJmxTest.java:111) ~[test-classes/:?]
> at org.infinispan.statetransfer.RebalancePolicyJmxTest.testJoinAndLeaveWithRebalanceSuspended(RebalancePolicyJmxTest.java:36) ~[test-classes/:?]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5879) XSite client failover - ensure TcpTransportFactory.trySwitchCluster thread safety
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-5879?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño reassigned ISPN-5879:
--------------------------------------
Assignee: Galder Zamarreño
> XSite client failover - ensure TcpTransportFactory.trySwitchCluster thread safety
> ---------------------------------------------------------------------------------
>
> Key: ISPN-5879
> URL: https://issues.jboss.org/browse/ISPN-5879
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication, Remote Protocols
> Reporter: Matej Čimbora
> Assignee: Galder Zamarreño
> Priority: Critical
> Fix For: 8.1.0.Beta2
>
>
> When reusing a HotRod client with several threads, site can be accidentally switched multiple times by threads invoking TcpTransportFactory.trySwitchCluster. This occurs when the threads attain 'maxRetries' limit at the same time, each of them being able to invoke TcpTransportFactory..updateServers with different 'clusterAddresses' parameter. This can lead to unpredictable result (e.g. switching back to failed cluster, while the other one (backup) is up and running).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (ISPN-5879) XSite client failover - ensure TcpTransportFactory.trySwitchCluster thread safety
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-5879?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-5879:
-----------------------------------
Status: Open (was: New)
> XSite client failover - ensure TcpTransportFactory.trySwitchCluster thread safety
> ---------------------------------------------------------------------------------
>
> Key: ISPN-5879
> URL: https://issues.jboss.org/browse/ISPN-5879
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication, Remote Protocols
> Reporter: Matej Čimbora
> Assignee: Galder Zamarreño
> Priority: Critical
> Fix For: 8.1.0.Beta2
>
>
> When reusing a HotRod client with several threads, site can be accidentally switched multiple times by threads invoking TcpTransportFactory.trySwitchCluster. This occurs when the threads attain 'maxRetries' limit at the same time, each of them being able to invoke TcpTransportFactory..updateServers with different 'clusterAddresses' parameter. This can lead to unpredictable result (e.g. switching back to failed cluster, while the other one (backup) is up and running).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months