You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jignesh Dhruv (JIRA)" <ji...@apache.org> on 2010/08/03 23:35:16 UTC
[jira] Reopened: (CASSANDRA-1291) nodetool ring prints incorrect IP
address
[ https://issues.apache.org/jira/browse/CASSANDRA-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jignesh Dhruv reopened CASSANDRA-1291:
--------------------------------------
Its not working again. nodetool is displaying wrong IP in the ring command.
I see that you reverted back to use HashSet instead of LinkedHashSet and I believe that is where the problem is.
I had no issues with the last svn revision, writes/reads all were working great with that revision too.
Reopening the issue.
> 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.