cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaakko Laine (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-572) handle old gossip properly
Date Mon, 21 Dec 2009 09:32:18 GMT


Jaakko Laine updated CASSANDRA-572:

    Attachment: 572-03-unit-tests.patch

Fix ArrayIndex exception in case the first gossip a new node sees is leaving or left.

Use one state for all movement related gossip
Fix also some bugs related to pending ranges on the leaving node itself

A bunch of unit tests for node movement

> 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-01-fix-index-out-of-bounds.patch, 572-02-use-one-move-state.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