Hi,
If you are using datastax java driver, I think this might work.
http://docs.datastax.com/en/latest-java-driver-api/com/datastax/driver/core/policies/WhiteListPolicy.html
On Sep 11, 2017 2:28 AM, "Jeff Jirsa" wrote:
> There's not - you can disable native/binary to make it less likely, but
>
There's not - you can disable native/binary to make it less likely, but you
can't stop reads entirely because you need gossip up in order to have hints
deliver
What you can do is use severity to make the dynamic snitch MUCH less likely to
pick that node (and disable binary so it's not a coordin
Hello,
from time to time we have situations where node is down for longer period
(but less than max_hint_window_in_ms). After node is up and hints are
activly syncing to affected node, clients get inconsistent data (client
uses LOCAL_ONE consistency due to performance reasons).
Is any way exist t
