Yes, LOCAL_QUORUM is usually sufficient and I use this consistency level
often, but at times a stronger consistency level is desired. Even within a
single DC, blocking in a fixed size thread pool on multiple network calls
is less than ideal.
If light weight transactions are being adopted warmly by
While using LOCAL_QUORUM may be a solution in a lot of use cases, there are
definitely use cases where reading at full QUORUM is required, think finance,
medical, military. I think for these types of use cases using non blocking
behavior will be an incredible improvement in performance. Even for
Use local quorum, don't talk to remote dcs.
On Fri, Jan 8, 2016 at 1:41 PM Dominic Chevalier
wrote:
> Hello,
>
> tldr;
>
> It looks like StorageProxy.fetchRows blocking for read responses can get
> pretty bad during quorum reads involving many geographically distant data
> centers. If this is tru
Hello,
tldr;
It looks like StorageProxy.fetchRows blocking for read responses can get
pretty bad during quorum reads involving many geographically distant data
centers. If this is true, why doesn't the coordinator handle replies
asynchronously to keep over all throughput up?
Long;
I'm running a
