Assuming the rebuild is happening on a node in another DC, then there should not be an issue if you are using LOCAL_ONE. If the node is in the local DC (i.e., same DC as the client), I am inclined to think repair would be more appropriate than rebuild but I am not 100% certain.
On Mon, Aug 5, 2019 at 11:23 PM Jeff Jirsa <jji...@gmail.com> wrote: > No, not strictly sufficient - makes it much less likely though > > A client may connect to another node and still send the request to that > host if the snitch picks it. You can make THAT less likely with some snitch > trickery (setting the badness for the rebuilding host) via jmx > > On Aug 5, 2019, at 8:17 PM, Cyril Scetbon <cyril.scet...@free.fr> wrote: > > Hey guys, > > Can you confirm that disabling the native transport (nodetool > disablebinary) is enough with Cassandra 3.11+ to avoid clients hitting > inconsistent data on that node when they use LOCAL_ONE consistency ? > (Particularly when the node is rebuilding …) > I'd like to avoid any fancy client configuration like blacklisting nodes. > > Thanks > — > Cyril Scetbon > > -- - John
