Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <467069739.26201262632914714.JavaMail.jira@brutus.apache.org>
Date: Mon, 4 Jan 2010 19:21:54 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-665) Persist token ring across cluster
 restarts
In-Reply-To: <2093126385.22671262621998937.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-665:
------------------------------------------

The naive solution of just using the IP->token mapping wil already persist trades this problem for a new one: it would become difficult to change the IP of an existing node.  Granted, this is a rare operate -- but so is shutting down the entire cluster.

One way to address this is using UUIDs for identity (rather than IP, directly) and mapping UUID -> token, UUID -> IP separately.

> Persist token ring across cluster restarts
> ------------------------------------------
>
>                 Key: CASSANDRA-665
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-665
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.9
>
>
> This prevents users from shooting their foot by shutting down a cluster, then restarting it with a subset of the former nodes.

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