[
https://issues.jboss.org/browse/ISPN-3811?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-3811:
------------------------------------
I just saw this happening in StateTransferFunctionalTest.
After a merge/coordinator change, the new coordinator is supposed to add the new members
to the CH, but not as owners for any segments. However, in replicated mode, all the
members of the CH are considered owners, so the joiner can become a regular owner without
actually receiving the data.
Initial ST leaves node as member without data after MERGE
---------------------------------------------------------
Key: ISPN-3811
URL:
https://issues.jboss.org/browse/ISPN-3811
Project: Infinispan
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: State Transfer
Affects Versions: 6.0.0.Final
Reporter: Radim Vansa
Assignee: Dan Berindei
Priority: Critical
Labels: testsuite_stability
Under certain circumstances, JGroups can issue a MERGE view when a node is joining the
cache. The new node joins the cluster, and all nodes have the same cache topology (not
containing the joiner yet).
During the merge, the CH's are joined (through CHFactory.union) and as all report the
same topology/hash, the resulting hash is identical. However, the joiner is added to the
members list and therefore it can finish the initial state transfer, although no data have
been assigned to him.
Later, the coordinator starts rebalance and the node begins to receive some data, but the
thread which started the cluster manager (and should wait until the cluster becomes
properly replicated through initial ST) is already released.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)