Thank you Dipan, it makes sense now.
Cheers,
Anurag
On Sun, Jul 16, 2023 at 12:43 AM Dipan Shah wrote:
> Hello Anurag,
>
> In Cassandra, Strong consistency is guaranteed when "R + W > N" where R is
> Read consistency, W is Write consistency and N is the Replication Factor.
>
> So in your case,
Hello Anurag,
In Cassandra, Strong consistency is guaranteed when "R + W > N" where R is
Read consistency, W is Write consistency and N is the Replication Factor.
So in your case, R(2) + W(1) = 3 which is NOT greater than your replication
factor(3) so you will not be able to guarantee strong cons
thank you Jeff,
it makes more sense now. How about I write with ONE consistency,
replication factor = 3 and read consistency is QUORUM. I am guessing in
that case, I will not have the empty read even if it is happened
immediately after the write request, let me know your thoughts ?
Cheers,
Anurag
Consistency level controls when queries acknowledge/succeed
Replication factor is where data lives / how many copies
If you write at consistency ONE and replication factor 3, the query finishes
successfully when the write is durable on one of the 3 copies.
It will get sent to all 3, but it’ll
Hello Users,
I am new to Cassandra and trying to understand the architecture of it. If I
write to ONE node for a particular key and have a replication factor of 3,
would the written key will get replicated to the other two nodes ? Let me
know if I am thinking incorrectly.
Thanks,
Anurag
