[infinispan-issues] [JBoss JIRA] Updated: (ISPN-361) Document the effects of concurrent state transfer/rehashing

[ https://jira.jboss.org/jira/browse/ISPN-361?page=com.atlassian.jira.plugi... ] Manik Surtani updated ISPN-361: ------------------------------- Summary: Document the effects of concurrent state transfer/rehashing (was: state transfer when multiple nodes join) Fix Version/s: 4.0.1.Final Description: Rehashing/state transfer for joiners is sequential. The process should be detailed in a wiki page to help people understand this process. "How are the overlapping rehashing/state transfers managed. E.g. one node JVM crashes -> rehashing/state transfers, the crashed node comes back to alive (e.g. through automatic restart) before the rehashing/state transfer is completed. What is the policy to manage this situation? - add a UT to catch the behavior of the previous scenario - add a wiki page to describe state transfer and how multiple nodes join etc" was: How are the overlapping rehashing/state transfers managed. E.g. one node JVM crashes -> rehashing/state transfers, the crashed node comes back to alive (e.g. through automatic restart) before the rehashing/state transfer is completed. What is the policy to manage this situation? - add a UT to catch the behavior of the previous scenario - add a wiki page to describe state transfer and how multiple nodes join etc Affects: [Documentation (Ref Guide, User Guide, etc.)] Complexity: Low -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira