Search code examples
datastax-enterprisecassandra-2.1

Datastax Enterprise: Added Node serviing data before replication is complete


We have a cluster of 3 Cassandra 2.1 nodes in Datastax Enterprise; we had to replace one of our nodes that had a hardware failure. When we added the third node, it immediately started to serve requests before it had completed data synchronization.

My question: Is there a way to mark the node as not available until we know replication is complete? We can't have this machine in our production rotation. I took the node down but while it's down its not backfilling data.

Please let me know, thanks,

Bob Glassett


Solution

  • Try starting the node with following option

    -Djoin_ring=false
    

    After completing required task on your node, add the node to the ring

    nodetool join <options>