[
https://issues.apache.org/jira/browse/CASSANDRA-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207872#comment-13207872
]
Peter Schuller commented on CASSANDRA-3412:
-------------------------------------------
{quote}
I think we can do a little better than that – we only have to leave ownership
undefined if the KS actually have different replication settings.
{quote}
Agreed.
{quote}
Shrug, I don't have a problem with just printing out a line explaining why, at
the bottom.
{quote}
The reason I didn't suggest it is that it might break scripts. On the one hand,
you normally shouldn't use human readable tool output for important scripting,
but on the other hand we don't offer a real alternative so I have to assume
that's what people do (as I have done myself).
Anyways, I'm not too fussed personally. If complaints come in I'd rather just
provide something intended for scripting than be forever locked into not
changing output.
> 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
