Re: Measuring Read Repairs

[Jeff Jirsa]

Or enable tracing, and check the tracing output for read repair lines.


On Fri, Aug 25, 2017 at 12:30 PM, Akhil Mehra  wrote:

> 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 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 tell if read repairs are happening based on this query?
>
> I’m not seeing anything in the logs.
>
>
>
>
>

Re: Measuring Read Repairs

[Akhil Mehra]

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 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 tell if read repairs are happening based on this query?
>  
> I’m not seeing anything in the logs.
>  
>  

Measuring Read Repairs

[Chuck Reynolds]

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 tell if read repairs are happening based on this query?

I’m not seeing anything in the logs.