Hi Robert, sorry for the confusion. Perhaps write_survey is not my solution (unfortunetaly I cant get it to work, so I dont really know). I just thought that it *could* be my solution.
What I actually want: I want to be able to start a new node, without it starting to serve reads prematurely. I want cassandra to wait for me to confirm "everything is ok, now serve reads". Possible solutions so far: A) When starting a new node with auto_bootstrap=false, then I get a node that has no data, but serves reads. In my opinion it would be cleaner if it would stay in a joining state where it only receives writes. B) Disabling join_ring on my new node does nothing. The new node will not have a token. I cant see it in "nodetool status". Therefore I assume it will not receive any writes. C) write_survey unfortunetaly does not seem to work for me: My new node, which I start with survey-mode, gets writes from other nodes and shows as "joining" in the ring. Which is good! But does not get a schema, so it throws exceptions when receiving these writes. I assume its just a bug in 2.0. Disclaimer: I am using C* 2.0, with which I can't get the desire behaviour (or at least I don't know how). kind regards, Christian On Tue, Aug 4, 2015 at 7:12 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Tue, Aug 4, 2015 at 6:19 AM, horschi <hors...@gmail.com> wrote: > >> I would like to separate these steps: >> 1. assign tokens >> 2. have the node in a joining state, so that I can copy in data >> 3. mark the node as ready >> > > >> Did anyone ever use write_survey for such a partial bootstrapping? >> > > What you're asking doesn't make sense to me. > > What does "partial bootstrap" mean? Where are you getting the data from? > How are you "copying in data" and why do you need the node to be "in a > joining state" to do that? > > https://issues.apache.org/jira/browse/CASSANDRA-6961 > > Explains a method by which you can repair a partially joined node. In what > way does this differ from what you want? > > =Rob > >
