cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5131) Make the TOKENS app state the canonical place for tokens
Date Wed, 20 Nov 2013 16:19:35 GMT

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

Brandon Williams commented on CASSANDRA-5131:
---------------------------------------------

I think we're actually OK, but I'll doublecheck.  Certainly replacing a node now uses TOKENS
only, but that worked even without vnodes, so I think we're just left with the STATUS cruft.

> Make the TOKENS app state the canonical place for tokens
> --------------------------------------------------------
>
>                 Key: CASSANDRA-5131
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5131
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 2.1
>
>
> Currently we store legacy-style single token deployments in our old, hackish STATUS and
split on a comma delimeter, but store vnodes in the TOKENS app state properly.  We should
be able to put the single token in TOKENS as well in a 1.2 minor release, make that the minimum
release needed to go to 2.0, and remove the STATUS hacks for 2.0.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message