On Wed, Aug 5, 2015 at 2:08 AM, horschi <hors...@gmail.com> wrote: > So what I am trying to say is: Everytime you use auto_bootstrap=false, you > are entering a dangerous path. And I think this could be fixed, if > auto_bootstrap=false would leave the node in a write-only state. Then the > operator could still decide to override it with nodetool. >
That's why you only use auto_bootstrap=false in cases where you have already restored the data on the node, or when you are rebuilding a new DC and know not to ask the new nodes at CL.ONE. Your asking the wrong nodes for data in the rebuild-a-new-DC case does not indicate a problem with the auto_bootstrap false + rebuild paradigm. What makes you think you should be using it in any case other than rebuild-new-DC or "I restored my node's data with tablesnap"? As the bug I pasted you indicates, if you want to repair a node before having it join, use join_ring=false, repair it, and then join. https://issues.apache.org/jira/browse/CASSANDRA-6961 In what way does this functionality not meet your needs? I continue to believe you are trying to use auto_bootstrap:false in wrong cases and that the solution to your problem is to stop doing that. =Rob
