[
https://issues.jboss.org/browse/ISPN-3421?page=com.atlassian.jira.plugin....
]
Radim Vansa commented on ISPN-3421:
-----------------------------------
So do I understand the description correctly, that with e.g 3 owners this happens:
A B are old owners, C is new owner
C requests data from A
A leaves the cluster
C does not reroute the request for rest of the data to B
Or is this something else?
State Transfer can leave keys on < numOwners nodes for
transactional caches.
----------------------------------------------------------------------------
Key: ISPN-3421
URL:
https://issues.jboss.org/browse/ISPN-3421
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 5.2.7.Final
Reporter: Erik Salter
Assignee: Dan Berindei
Priority: Critical
There's a hole in state transfer mechanism that can occur when a node is leaving the
cluster, but it was creating the entries and was only able to replicate the data to some
of the nodes.
The problem occurs when the segment ownership of the node doesn't change after the
rebalance. Since state transfer does not request state for keys in which it is already an
owner, the cache could be left in a state where a key is resident < numOwners nodes.
In addition, this could be any subset of the primary OR backup nodes.
--
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