cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaakko Laine (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-572) handle old gossip properly
Date Sat, 19 Dec 2009 00:15:18 GMT


Jaakko Laine commented on CASSANDRA-572:

Sorry about the delay. I did this part again yesterday (somewhat different now after #603),
but had insufficient time to test it properly. The patch would seem OK, so as soon as I have
tested it a bit more, I'll submit it.

The problem earlier was how to handle state jump to 'leaving'. Now that pending ranges is
calculated every time and we know what direction a node was going last time, this is not a
problem anymore. You can expect a patch soon.

> handle old gossip properly
> --------------------------
>                 Key: CASSANDRA-572
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.5
>            Reporter: Jaakko Laine
>             Fix For: 0.5
>         Attachments: 572-handle-old-gossip.patch, use-same-APstate-for-all-node-state-gossip.patch
> (1) If a node has been moving in the ring, further bootstraps by other nodes will cause
errors as they are handling STATE_LEAVING gossip without having such member in token metadata.
> (2) When a node bootstraps, it handles all ep states in the order they happen to arrive.
If the first one to arrive has moved in the past (that is, it has STATE_LEAVING in its ep
state), getNaturalEndpoint will throw ArrayIndexOutOfBounds exception as sortedTokens.size()
== 0.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message