Hi Rob, let me try to give examples why auto_bootstrap=false is dangerous:
I just yesterday had the issue that we wanted to set up a new DC: Unfortunetaly we had one application that used CL.ONE (because its only querying static data and its read heavy). That application stopped working after we brought up the new DC, because it was querying against the new nodes. We are now changing it to LOCAL_ONE, then it should be Ok. But nevertheless: I think it would have been cleaner if the new node would not have served reads in the first place. Instead the operations people have to worry about the applications using the correct CL. Another, more general, issue with auto_bootstrap=false: When adding a new node to an existing cluster, you are basically lowering your CL by one. RF=3 with with quorum will read from two nodes. One might be the bootstrapped node, which has no data. Then you are relying on a single node to be 100% consistent. 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. Disclaimer: I am using C* 2.0. kind regards, Christian On Tue, Aug 4, 2015 at 10:02 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Tue, Aug 4, 2015 at 11:40 AM, horschi <hors...@gmail.com> wrote: > >> unless you specify auto_bootstrap=false :) >> > > ... so why are you doing that? > > Two experts are confused as to what you're trying to do; why do you think > you need to do it? > > =Rob > >
