[
https://issues.apache.org/jira/browse/CASSANDRA-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895305#action_12895305
]
Jonathan Ellis commented on CASSANDRA-1291:
-------------------------------------------
The confusing thing to me is that while I can picture situations where code
assumes the first node from calculateNaturalEndpoints is special, nodetool ring
doesn't hit calculateNaturalEndpoints at all [it's calculated purely from
StorageService's TokenMetadata]. So I don't see how LHS vs HS should matter at
all.
> 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.
