[
https://issues.apache.org/jira/browse/CASSANDRA-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893349#action_12893349
]
Nick Bailey commented on CASSANDRA-1291:
----------------------------------------
I believe Jignesh's change is almost certainly the problem. It's not
consistently reproduceable because it depends on the hash value of the endpoint.
Jignesh, you should modify RackUnawareStrategy as well and attach and submit
the patch.
> 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
> Fix For: 0.7 beta 1
>
>
> 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.
