cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "yangwei (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-5216) fix bug on decommission and removeNode
Date Sun, 03 Feb 2013 15:44:12 GMT
yangwei created CASSANDRA-5216:

             Summary: fix bug on decommission and removeNode
                 Key: CASSANDRA-5216
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.2.1
            Reporter: yangwei
             Fix For: 1.2.1

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:

View raw message