cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Alves (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3047) implementations of IPartitioner.describeOwnership() are not DC aware
Date Sun, 10 Jun 2012 19:06:44 GMT


David Alves commented on CASSANDRA-3047:

Hi jonathan

I'm not sure I completely understand your suggestion.

If I understand correctly the problem is that probe.effectiveOwnership(keyspace) is calculating
ring assignment percentages on multiple ring scenarios as if it was a single ring, correct?

If these values are incorrectly calculated how would separating the output per dc help?
> implementations of IPartitioner.describeOwnership() are not DC aware
> --------------------------------------------------------------------
>                 Key: CASSANDRA-3047
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Aaron Morton
>            Assignee: David Alves
>            Priority: Trivial
>             Fix For: 1.1.2
> see
> When a cluster the multiple rings approach to tokens the output from nodetool ring is
> 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:!default.jspa
For more information on JIRA, see:


View raw message