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

Reply via email to