And I’m not aware of any case where it’s a good idea to use SimpleStrategy
in Prod (be interested to hear if anyone else knows of one).
NetworkTopologyStrategy behaves the same as SimpleStrategy in the basic
case of one DC and Rack but gives you a good path to migrate to more
sophisticated
For sensitive data, I'd recommend to use at least RF=3. Especially if you
plan to use CL QUORUM, for example if you want to ensure consistency.
If you use QUORUM and RF=2 then a single failing node will make your data
unavailable.
For more information, please read
Thank you so much for answer.
So, in case of a high failure rate in my cluster, i have to increase the
replication factor or i have to use NetworkToplogy Strategy ?
That's it ?
Kindly.
2016-12-18 20:23 GMT+01:00 Matija Gobec :
> If you are reading and none of the
If you are reading and none of the replicas is online you will get an
exception on the read (tried x replicas but 0 responded) and your read will
fail. Writes on the other hand are going to go through only if your write
consistency is ANY. If your write consistency is ONE or anything upwards,
then
Hi,
Please, if we choose a replication factor =2 (simple strategy), so, we have
two replicas of data on the ring.
What happen in the case of all nodes containing replicas are down ?
Thank you so much for help.
Kind regards.