You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brian Gallew (JIRA)" <ji...@apache.org> on 2017/04/12 15:48:41 UTC
[jira] [Created] (CASSANDRA-13439) nodetool ring output should
reflect rack perturbation
Brian Gallew created CASSANDRA-13439:
----------------------------------------
Summary: nodetool ring output should reflect rack perturbation
Key: CASSANDRA-13439
URL: https://issues.apache.org/jira/browse/CASSANDRA-13439
Project: Cassandra
Issue Type: Improvement
Components: Distributed Metadata
Reporter: Brian Gallew
Currently, "nodetool ring $KEYSPACE" shows ownership based entirely upon token distribution. However, the *actual* ownership must also account for rack information. As an example, for a table with RF=3 in a cluster with three racks, if the ring order of nodes/racks is, e.g. node1-rack1, node2-rack2, node3-rack1, node-4rack2, node5-rack3, ...
It will turn out that node5 shares ownership with node1, node2, node3, and node4 because of rack distribution rules. Not only is this potentially unexpected, it's also somewhat difficult to reason about exactly how the data will be distributed. It would be really convenient if nodetool could tell us this distribution.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)