You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "William Montaz (JIRA)" <ji...@apache.org> on 2013/09/03 18:28:51 UTC
[jira] [Created] (CASSANDRA-5973) system.peers 'tokens' field not
in sync after cassandra-shuffle operation
William Montaz created CASSANDRA-5973:
-----------------------------------------
Summary: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira