Chuck Reynolds wrote:
>
> I’m running queries based on the token ranges to initiate read repairs
> across datacenter.
>
> Example query with CONSISTENCY set to ALL
> SELECT *token*(*test_guid*), test_guid FROM test_table WHERE
> token(test_guid)>6546138161478345924 AND token(test
You can run nodetool tpstats on your nodes and check the output for the
ReadRepairStage.
Cheers,
Akhil
> On 26/08/2017, at 6:54 AM, Chuck Reynolds wrote:
>
> I’m running queries based on the token ranges to initiate read repairs across
> datacenter.
>
> Example query wi
I’m running queries based on the token ranges to initiate read repairs across
datacenter.
Example query with CONSISTENCY set to ALL
SELECT token(test_guid), test_guid FROM test_table WHERE
token(test_guid)>6546138161478345924 AND token(test_guid)<6571069709219758671;
Is there a way to t
Thanks Sam - a couple of subtleties there that we missed in our review.
Cheers
Ben
On Tue, 30 Aug 2016 at 19:42 Sam Tunnicliffe wrote:
> Just to clarify a little further, it's true that read repair queries are
> performed at CL ALL, but this is slightly different to a regular,
> user-initiated
Just to clarify a little further, it's true that read repair queries are
performed at CL ALL, but this is slightly different to a regular,
user-initiated query at that CL.
Say you have RF=5 and you issue read at CL ALL, the coordinator will send
requests to all 5 replicas and block until it receiv
In case anyone else is interested - we figured this out. When C* decides it
need to do a repair based on a digest mismatch from the initial reads for
the consistency level it does actually try to do a read at CL=ALL in order
to get the most up to date data to use to repair.
This led to an interest
Looking at the wiki for the read path (
http://wiki.apache.org/cassandra/ReadPathForUsers), in the bottom diagram
for reading with a read repair, it states the following when "reading from
all replica nodes" after there is a hash mismatch:
If hashes do not match, do conflict resolution. First step
read_repair_chance: Probability (0.0-1.0) with which to perform read repairs
on CL.ONE reads
Default is 1.0 your CL.ONE reads will trigger read repairs for all reads.
You can update your column families definition to reduce that chance. For
the CL.ALL writes you can consider turning it off by
Hello,
I have a 3-node ring at RF=3 that is doing reads & writes. I am using two
types of consistency levels.
- write ALL,read ONE for one set of column families
- write QUORUM, read ONE for another set of families
Every day, I have a cron job that runs a nodetool repair on each node. The
n
