Hi Rob,
> 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. > The node is "wrong" only because its currently bootstrapping. So imho Cassandra should not serve any reads in such a case. > > 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"? > These two cases are my example use-cases. I don't know if there are any other cases, perhaps there is. > > 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 see two reasons why join_ring=false does not help with my issue or I misunderstand: - When I set up a new node and I start it with join_ring=false, then it does not get any tokens, right? (I tried it, and that was what I got) How can I run "nodetool repair" when the node doesn't have any tokens? - A node that is not joining the ring, will not receive any writes, right? So if I run repair in a unjoined state for X hours, then I will miss X hours worth of data afterwards. The only solution I see seems to be write_survey. I will do some tests with it, once 2.0.17 is out. I will post my results :-) kind regards, Christian
