[
https://issues.apache.org/jira/browse/CASSANDRA-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894810#action_12894810
]
Jignesh Dhruv commented on CASSANDRA-1291:
------------------------------------------
Hi Jonathan,
What I am seeing is that with RF=2 or more and endpoints being HashSet,
displays incorrect nodes/ip in the nodetool ring command. Changing HashSet to
LinkedHashSet displays ring correctly with unique ip addresses. I rely on
nodetool ring command to determine what nodes are up and their load
distribution.
Let me know if I have not answered your question?
Thanks,
Jignesh
> nodetool ring prints incorrect IP address
> -----------------------------------------
>
> Key: CASSANDRA-1291
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1291
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.7 beta 1
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 0.7 beta 1
>
> Attachments: 1291.txt
>
>
> Nodetool's ring output on trunk seems to duplicate an ipaddress instead of
> printing them all.
> To reproduce: spin up a 3 node cluster and create a keyspace, examine
> nodetool ring. One ip address will show up twice, though the tokens are
> correctly displayed for the three machines.
> This is a cosmetic error, if you call getLiveNodes via JMX you can see all
> three IPs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
