[
https://issues.jboss.org/browse/ISPN-4549?page=com.atlassian.jira.plugin....
]
Dan Berindei edited comment on ISPN-4549 at 10/28/14 5:32 AM:
--------------------------------------------------------------
[~galderz] the problem was with the "it waits for the coordinator to not be in a
rebalancing mode" step, which was not done correctly (i.e. the test considered that
the rebalance was done before it had even started).
was (Author: dan.berindei):
[~galderz] the problem was with the "it waits for the coordinator to not be in a
rebalancing mode", which was incorrect.
StateTransferSuppressForMemcacheIT.testRebalanceWithJoinedNodeStop random failures
----------------------------------------------------------------------------------
Key: ISPN-4549
URL:
https://issues.jboss.org/browse/ISPN-4549
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Server
Affects Versions: 7.0.0.Alpha5
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Blocker
Labels: testsuite_stability
Fix For: 7.0.0.Final
The test checks that the rebalance is complete by waiting for the
{{CommittedViewAsString}} reported by the RpcManager MBean to be
{{"DefaultConsistentHash\{numSegments=60, numOwners=2, members=\[node0/" +
getCacheManagerName() + ", node1/" + getCacheManagerName() + "\]\}"}}
and the {{PendingViewAsString}} to be {{null}}.
But immediately after the 3rd server is stopped, the coordinator installs a topology with
exactly the same string representation. It only starts the rebalance after that.
So the test could start checking the number of entries before the rebalance actually
started.
Failure in CI:
http://ci.infinispan.org/viewLog.html?buildId=9804&tab=buildResultsDi...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)