You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alexey Zotov (JIRA)" <ji...@apache.org> on 2012/09/18 12:59:09 UTC

[jira] [Updated] (CASSANDRA-4677) Change description of nodetool ring command

     [ https://issues.apache.org/jira/browse/CASSANDRA-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Zotov updated CASSANDRA-4677:
------------------------------------

    Attachment: nodetool_ring_description.patch
    
> Change description of nodetool ring command
> -------------------------------------------
>
>                 Key: CASSANDRA-4677
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4677
>             Project: Cassandra
>          Issue Type: Task
>          Components: Tools
>    Affects Versions: 1.1.5
>            Reporter: Alexey Zotov
>            Priority: Trivial
>              Labels: ring
>         Attachments: nodetool_ring_description.patch
>
>
> Additional option of 'nodetool ring' command is not documented. 
> Old variant:
> {code}
>   ring                   - Print information about the token ring
> {code}
> New variant
> {code}
>   ring [keyspace]        - Print information about the token ring for a given keyspace (for all keyspaces if it is not specified)
> {code}
> Patch has been attached.
> Some history (I think it will be useful for someone who will have the same problem): 
> I have 4-nodes cluster. One of nodes is located in other DC (DC2). I've met the problem that 'nodetool ring' shows that node in DC2 'Owns 0.00%'. I've found following questions:
> http://www.datastax.com/support-forums/topic/owns-in-nodetool
> http://mail-archives.apache.org/mod_mbox/cassandra-user/201202.mbox/%3C323DBC99-8519-4E86-B69B-6520D53FA5CF@humbaba.net%3E
> and task with fix:
> https://issues.apache.org/jira/browse/CASSANDRA-3412
> So you should use 'nodetool ring keyspace' for getting right information. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira