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

[Manik Surtani (JIRA)]

     [ https://jira.jboss.org/jira/browse/ISPN-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manik Surtani resolved ISPN-361.
--------------------------------

    Fix Version/s:     (was: 4.0.1.Final)
       Resolution: Won't Fix


Rehashing is being revised anyway with streamed rehashing, etc.  Will document as a part of this.

> Document the effects of concurrent state transfer/rehashing
> -----------------------------------------------------------
>
>                 Key: ISPN-361
>                 URL: https://jira.jboss.org/jira/browse/ISPN-361
>             Project: Infinispan
>          Issue Type: Feature Request
>            Reporter: Mircea Markus
>            Assignee: Manik Surtani
>
> Rehashing/state transfer for joiners is sequential.  The process should be detailed in a wiki page to help people understand this process.
> From Mircea's original comment on this JIRA:
> "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"

-- 
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