[
https://issues.apache.org/jira/browse/CASSANDRA-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895307#action_12895307
]
Jignesh Dhruv commented on CASSANDRA-1291:
------------------------------------------
I believe it does.
I did put some debugging statements in calculateNaturalEndpoints in
RackAwareStrategy before and that is when I realized that the problem is in the
way endpoints are stored.
So here is my usecase:
I started up a new cluster, no data has been inserted yet. I create the schema
with RF=3 on one node which gets replicated on all other nodes. Now I run the
nodetool ring command and I see incorrect/duplicate ips in the ring command.
Changing HashSet back to LinkedHashSet does solve the problem.
> 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.
