[
https://issues.apache.org/jira/browse/CASSANDRA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293974#comment-13293974
]
Jonathan Ellis commented on CASSANDRA-3047:
-------------------------------------------
I like where you're going here. Maybe split the DCs out even more explicitly?
{noformat}
Keyspace: myKeyspace
Replication Strategy: NetworkTopologyStrategy
DC1
===
Replicas: 1
Address Rack Status State Load Effective-Ownership
Token
127.0.0.1 RAC1 Up Normal 40 KB 100.0% 0
DC2
===
Replicas: 1
Address Rack Status State Load Effective-Ownership
Token
127.0.0.2 RAC1 Up Normal 40 KB 50.0% 0
127.0.0.3 RAC2 Up Normal 40 KB 50.0% 8...
DC3
===
Replicas: 2
Address Rack Status State Load Effective-Ownership
Token
127.0.0.4 RAC1 Up Normal 40 KB 50.0% 0
127.0.0.5 RAC1 Up Normal 40 KB 50.0% 4...
127.0.0.6 RAC2 Up Normal 40 KB 50.0% 8...
127.0.0.7 RAC2 Up Normal 40 KB 50.0% 12...
{noformat}
> implementations of IPartitioner.describeOwnership() are not DC aware
> --------------------------------------------------------------------
>
> Key: CASSANDRA-3047
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3047
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Aaron Morton
> Assignee: David Alves
> Priority: Trivial
> Fix For: 1.1.2
>
>
> see http://www.mail-archive.com/[email protected]/msg16375.html
> When a cluster the multiple rings approach to tokens the output from nodetool
> ring is incorrect.
> When it uses the interleaved token approach (e.g. dc1, dc2, dc1, dc2) it will
> be correct.
> It's a bit hacky but could we special case (RP) tokens that are off by 1 and
> calculate the ownership per dc ? I guess another approach would be to add
> some parameters so the partitioner can be told about the token assignment
> strategy.
--
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
