[
https://issues.apache.org/jira/browse/CASSANDRA-5973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler resolved CASSANDRA-5973.
---------------------------------------
Resolution: Not a Problem
Reproduced In: 1.2.8, 1.2.6 (was: 1.2.6, 1.2.8)
Closing as not a problem. Shuffle has had some issues and discussion on the
mailing lists as probably a less than ideal way to migrate to vnodes.
> system.peers 'tokens' field not in sync after cassandra-shuffle operation
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-5973
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5973
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 1.2.8 and Cassandra 1.2.6
> Reporter: William Montaz
>
> After shuffling vnodes, system.peers contains only one token per peer
> For instance ->
> select tokens from system.peers where peer = 'xx.xx.xx.xx';
> tokens
> -------------------------
> {'8428746505504052053'}
> I discovered this problem with java driver's TokenAwarePolicy that seems to
> be using system.peers data to distribute requests accross the cluster wich
> leads to contusions because a lot of requests go to the wrong nodes
--
This message was sent by Atlassian JIRA
(v6.2#6252)
