[
https://issues.apache.org/jira/browse/CASSANDRA-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893254#action_12893254
]
Christopher Gist commented on CASSANDRA-1291:
---------------------------------------------
I have also observed nodetool ring reporting duplicate IPs on the latest trunk.
This was with a 2 node cluster and a keyspace with RF=2 and
RackUnawareStrategy. The correct IPs were reported with getLiveNodes via JMX.
After adding a keyspace with RF=1, the output of nodetool ring is as expected
with the correct IPs.
I think this behaviour might be related to nodetool ring using the range of the
first non-system keyspace in StorageService.getRangeToEndpointMap(null).
> 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.
