If zone a or b goes dark I want to keep my cluster alive with QUORUM on
reading. That's why I'm imagine solve this using another node in a
different location.
Thanks
On 15-09-2017 22:32, kurt greaves wrote:
> You can add a tiny node with 3 tokens. it will own a very small amount
> of data and
You can add a tiny node with 3 tokens. it will own a very small amount of
data and be responsible for replicas of that data and thus included in
quorum queries for that data. What is the use case? This won't give you any
real improvement in meeting consistency.
I've finished the migration to NetworkTopologyStrategy using
GossipingPropertyFileSnitch.
Now I have 4 nodes at zone a (rack1) and another 4 nodes at zone b
(rack2) only one dc, there's no zone c at Frankfurt.
Can I get QUORUM consistency for reading (for writing I'm using ANY)
adding a tiny
data will be distributed amongst racks correctly, however only if you are
using a snitch that understands racks and also NetworkTopologyStrategy.
SimpleStrategy doesn't understand racks or DCs. You should use a snitch
that understands racks and then transition to a 2 rack cluster, keeping
only 1
Hi list,
CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy',
'replication_factor': '2'} AND durable_writes = true;
I'm using C* 3.11.0 with 8 nodes at aws, 4 nodes at zone a and the other
4 nodes at zone b. The idea is to keep the cluster alive if zone a or b
goes dark and keep
