cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaakko Laine (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-435) unbootstrap
Date Thu, 12 Nov 2009 09:12:39 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776917#action_12776917
] 

Jaakko Laine commented on CASSANDRA-435:
----------------------------------------

When node is decommisioned, should it delete its saved token? If the same node is brought
back online without manual data deletion, it will enter the ring without proper bootstrap.


> unbootstrap
> -----------
>
>                 Key: CASSANDRA-435
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-435
>             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,
0002-move-more-generic-streaming-code-into-Streaming.java.txt, 0003-add-leaving-mode.txt,
0004-simplify-getChangedRangesForLeaving.txt, 0005-update-tokenmetadata-before-removing-obsolete-ranges.patch,
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.


Mime
View raw message