Thanks a lot Erick for your help and support.
Regards
Manish
On Wed, Sep 21, 2022, 19:12 Erick Ramirez wrote:
> Just to circle back here, I've reviewed the trace output and it shows
> multiple requests fired off for lookups on the `roles` table which
> indicated to me that the default
Just to circle back here, I've reviewed the trace output and it shows
multiple requests fired off for lookups on the `roles` table which
indicated to me that the default `cassandra` superuser is being used. To be
clear, the original read request is being executed at the configured
consistency BUT
I lost the beginning of the thread but I raised what seems the same
issue recently in this list.
I have a worldwide c* cluster with 3dcs (eu, us, ap 8nodes each). For
whatever reason I have read with consistency set to local_quorum which
trigger reads on other dc(s). I would say it's 1% of
Would you be open to temporarily posting the full CQL command + full trace
output to gist.github.com? I'd like to see what it shows. Cheers!
>
Thanks Erick for the response.
read_repair_chance is 0. Can speculative_retry cause this? We have that set
at 99 percentile.
Regards
Manish
On Wed, Sep 21, 2022 at 11:17 AM Erick Ramirez
wrote:
> It sounds like read-repair chance is enabled on the table. Check the table
> schema for a
