You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Jan Algermissen <al...@icloud.com> on 2017/06/18 14:07:06 UTC
Write / read cost of *QUORUM
Hi,
my understanding is that
- for writes using any of the quorum CLs will not put more overall load
on the cluster because writes will be sent to all nodes responsible for
a partition anyhow. So quorum only increases response time of the
coordinator, not cluster load.
Correct?
- for reads all quorum CLs will yield more requests sent by the
coordinator to other nodes and hence *QUORUM reads definitely increase
cluster load. (And of course response time of the coordinator, too).
Correct?
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org
Re: Write / read cost of *QUORUM
Posted by Vladimir Yudovin <vl...@winguzone.com>.
Hi,
yes, you are write. Actually write with QUORUM will cause to coordinator to wait for reply from other nodes, but I guess it's negligible.
Best regards, Vladimir Yudovin,
Winguzone - Cloud Cassandra Hosting
---- On Sun, 18 Jun 2017 10:07:06 -0400 Jan Algermissen <algermissen1971@icloud.com> wrote ----
Hi,
my understanding is that
- for writes using any of the quorum CLs will not put more overall load
on the cluster because writes will be sent to all nodes responsible for
a partition anyhow. So quorum only increases response time of the
coordinator, not cluster load.
Correct?
- for reads all quorum CLs will yield more requests sent by the
coordinator to other nodes and hence *QUORUM reads definitely increase
cluster load. (And of course response time of the coordinator, too).
Correct?
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org