[
https://issues.apache.org/jira/browse/CASSANDRA-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207454#comment-13207454
]
Peter Schuller commented on CASSANDRA-3412:
-------------------------------------------
Technically speaking, even making assumptions about DC is "incorrect" unless
those assumptions are tied to the choice of replication strategy. My point
here, is that a solution which is strictly correct and works with any
replication strategy would either have to be strategy specific, or blackbox the
details (such as our tool does). So I would suggest that it's actually okay to
try to generalize it and pick the widest keyspace if not otherwise picked; it
seems more "future proof" to assume the RF varies by KS, than to make
assumptions about the replication strategy. Especially if the alternative
doesn't get us the "true" ownership and only gets us the per-DC ring
information.
> make nodetool ring ownership smarter
> ------------------------------------
>
> Key: CASSANDRA-3412
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3412
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jackson Chung
> Assignee: Vijay
> Priority: Minor
>
> just a thought.. the ownership info currently just look at the token and
> calculate the % between nodes. It would be nice if it could do more, such as
> discriminate nodes of each DC, replica set, etc.
> ticket is open for suggestion...
--
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
