[infinispan-issues] [JBoss JIRA] (ISPN-2357) New coordinator installs old CH containing crashed members

Dan Berindei (JIRA) jira-events at lists.jboss.org
Wed Oct 3 07:59:03 EDT 2012


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

Dan Berindei updated ISPN-2357:
-------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/1358


When a node becomes the coordinator, it should not include nodes that
that didn't respond to the cache status request in the consistent hash.

Synchronize broadcasting of CH_UPDATE commands so that it's not possible
for the cluster members to receive them out-of-order.

                
> New coordinator installs old CH containing crashed members
> ----------------------------------------------------------
>
>                 Key: ISPN-2357
>                 URL: https://issues.jboss.org/browse/ISPN-2357
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: State transfer
>    Affects Versions: 5.2.0.Alpha4
>            Reporter: Erik Salter
>            Assignee: Dan Berindei
>             Fix For: 5.2.0.Beta1
>
>
> After merging the round of pull requests today (including ISPN-2349), there still is an issue where a killed node can appear in the CH even after JGroups passes up the new view.  This appears to happen when the old coordinator was killed.
> Obviously, if the CH contains the old member, writes that map to the segments previously owned by the dead node will fail.
> Here are ISPN trace logs.  You are looking for erm-cluster.
> http://dl.dropbox.com/u/50401510/5.2.0.ALPHA4/relay2/10.30.12.83/server.log.gz (phl-dg1)
> http://dl.dropbox.com/u/50401510/5.2.0.ALPHA4/relay2/10.30.12.84/server.log.gz (phl-dg2)
> http://dl.dropbox.com/u/50401510/5.2.0.ALPHA4/relay2/10.30.12.83/server.log.gz (phl-dg3, the node that was killed)

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


More information about the infinispan-issues mailing list