Re: cassandra getendpoints do not match with tracing

2018-06-25 Thread CPC
Any ideas? below is getendpoint result for a specific pk 172.16.5.235 172.16.5.229 172.16.5.228 172.16.5.223 172.16.5.234 172.16.5.241 and below is a trace with same pk Preparing statement [Native-Transport-Requests-2] | 2018-06-22 16:33:21.118000 | 172.16.5.242 | 6757

cassandra getendpoints do not match with tracing

2018-06-22 Thread CPC
Hi all, Recently we added some nodes to our cluster. After adding nodes we noticed that when we nodetool getendpoints tims "MESSAGE_HISTORY" partitionkey1 it reports three nodes per dc with 6 nodes in total which is expected since RF is 3. But when we run a query with local_one and tracing on ,