cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-435) unbootstrap
Date Wed, 11 Nov 2009 13:41:39 GMT


Jonathan Ellis commented on CASSANDRA-435:

1) LEAVING/NORMAL don't get re-broadcast though, so they remain part of the app state but
they won't ever be seen again by onChange.  So as long as LEFT isn't part of the same gossip
as leaving (and the sleep ensures it won't) in practice LEFT is already the last thing gossipped
(and we shut down the gossiper right afterwards).  This works as planned in my testing.  I'm
fine with patches improving this but it's not strictly necessary.

2) No, the pending ranges aren't to say "i'm busy streaming" but "when the planned ring changes
finish, this will be my range, so I need writes for that range in the meantime so I'm not
out of date when the change-over happens."  So the right place to remove those is in the STATE_LEFT
change.  I will add it there.

I will look at the 04 patch shortly.

> unbootstrap
> -----------
>                 Key: CASSANDRA-435
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.5
>         Attachments: 0001-CASSANDRA-435-clean-up-transfer-code-from-BMVH-move-t.txt,, 0003-add-leaving-mode.txt,
0004-simplify-getChangedRangesForLeaving.txt, 435-modify-update_leaving_ranges.txt
> add JMX command to tell a node to decommission itself (moving its data to the next node
on the ring)

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

View raw message