cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-5216) fix bug on decommission and removeNode
Date Mon, 04 Feb 2013 19:10:17 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brandon Williams resolved CASSANDRA-5216.
-----------------------------------------

    Resolution: Fixed

Good work, thanks.  Committed.
                
> fix bug on decommission and removeNode
> --------------------------------------
>
>                 Key: CASSANDRA-5216
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5216
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.1
>            Reporter: yangwei
>            Assignee: yangwei
>              Labels: gossip
>             Fix For: 1.2.1
>
>         Attachments: 0001-fix-isAlive-bug-on-decommission.patch, 0002-fix-expireTime-bug-on-removeNode.patch,
0003-fix-expireTime-bug-on-handleStateRemoving-after-rebo.patch
>
>
> 1. If one node decommissioned, the epState.isAlive is always true since it is DEAD_STATES
in convict(). 0001 patch fixes that.
> 2. If we removeNode B on A,  we should put expireTime of B in expireTimeEndpointMap of
A, otherwise the epState of B will never be removed from gossip entirely. 0002 patch fixes
that.
> 3. After removeNode B, C reboots and receives epState of B. Since B is not in the tokenMetadata,
C just wipes away B without recording B's expireTime. In this case, B will be always in gossip.
0003 patch fixes that.

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

Mime
View raw message