[ https://issues.jboss.org/browse/ISPN-1365?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-1365: -------------------------------- Assignee: Dan Berindei (was: Manik Surtani) Fix Version/s: 5.1.0.ALPHA1 5.1.0.FINAL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1365?page=com.atlassian.jira.plugin.... ] Erik Salter commented on ISPN-1365: ----------------------------------- For the second case, how do we manage this in production? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1365?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-1365: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/522 Distributed tasks were allowed to execute on a joining node before it was finished starting. That meant a distributed task could modify a key before the rehash, but then during the rehash another node could push an old value and overwrite it, resulting in data loss. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1365?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-1365: ------------------------------------ It turns out Erik's problem is not caused by the merge, but by the partitioning itself. He is using ISPN locks to ensure that external resources can only have a single a single owner, so any partitioning will allow multiple owners and break his model. His conclusion was that in production the load balancer will only connect to the nodes that are part of the cluster, so when a node starts up in a cluster by itself it will not receive any client requests until it has finished merging with the initial cluster. This will ensure the integrity of the model. A subsequent partition in the cluster ca still break his model, but the rehashing process can't help there. Note that the attached pull request solves a related problem when the node joins the cluster normally, *not* the 2) scenario in my Sep 4 comment. Somehow my environment changed and I'm not seeing any merge views, although my JGroups configuration is the same. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira