cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Overton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4121) TokenMetadata supports multiple tokens per host
Date Mon, 09 Jul 2012 16:47:34 GMT

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

Sam Overton commented on CASSANDRA-4121:
----------------------------------------

updateNormalTokens has to remove any existing token mapping(s) from tokenToEndpointMap and
remove the endpoint from bootstrapping/leaving/moving collections. resetEndpoints is just
storing which endpoints we have already done this for, to ensure it is only done once for
each endpoint, the first time we see it when iterating through tokenPairs.

The method should probably take Multimap<InetAddress, Token> instead of a Set<Pair<Token,
InetAddress>> which would simplify this logic somewhat.
                
> TokenMetadata supports multiple tokens per host
> -----------------------------------------------
>
>                 Key: CASSANDRA-4121
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4121
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Sam Overton
>            Assignee: Sam Overton
>              Labels: vnodes
>             Fix For: 1.2
>
>
> _Edit0: Append patch information._
> h3. Patches
> ||Compare||Raw diff||Description||
> |[01_support_multiple_tokens_per_host|https://github.com/acunu/cassandra/compare/top-bases/p/4121/01_support_multiple_tokens_per_host...p/4121/01_support_multiple_tokens_per_host]|[01_support_multiple_tokens_per_host.patch|https://github.com/acunu/cassandra/compare/top-bases/p/4121/01_support_multiple_tokens_per_host...p/4121/01_support_multiple_tokens_per_host.diff]|Support
associating more than one token per node|
> ----
> _Note: These are branches managed with TopGit. If you are applying the patch output manually,
you will either need to filter the TopGit metadata files (i.e. {{wget -O - <url> | filterdiff
-x*.topdeps -x*.topmsg | patch -p1}}), or remove them afterward ({{rm .topmsg .topdeps}})._

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message