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

Vijay updated CASSANDRA-6811:
-----------------------------

    Attachment: 0001-CASSANDRA-6811-v2.patch

Sorry, I misunderstood the comment thinking nodetool status doesn't need a 
fix...
Please see the attached, actually it fixes the joining status for Multi DC 
setup. (http://pastebin.com/QUqcPJen)

NOTE: 
I did a little bit of refactoring to reuse the code, hope it is ok.
Effective ownership for nodes might be broken before and after this patch, 
since every line shows the host ownership not the line items ownership.

> nodetool no longer shows node joining
> -------------------------------------
>
>                 Key: CASSANDRA-6811
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6811
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 1.2.16
>
>         Attachments: 0001-CASSANDRA-6811-v2.patch, ringfix.txt
>
>
> When we added effective ownership output to nodetool ring/status, we 
> accidentally began excluding joining nodes because we iterate the ownership 
> maps instead of the the endpoint to token map when printing the output, and 
> the joining nodes don't have any ownership.  The simplest thing to do is 
> probably iterate the token map instead, and not output any ownership info for 
> joining nodes.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to