[
https://issues.apache.org/jira/browse/CASSANDRA-20581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaydeepkumar Chovatia updated CASSANDRA-20581:
----------------------------------------------
Source Control Link:
https://github.com/apache/cassandra/commit/bf2c1c124e90f67b6e0bbec6b63af9946831ad70
> Improved observability in AutoRepair to report both expected vs. actual
> repair bytes and expected vs. actual keyspaces
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-20581
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20581
> Project: Apache Cassandra
> Issue Type: Task
> Components: Consistency/Repair
> Reporter: Jaydeepkumar Chovatia
> Assignee: Jaydeepkumar Chovatia
> Priority: Normal
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The current AutoRepair framework has enough visibility to know which nodes
> are going through repair, the duration they ran repair, the token ranges
> repaired, the failed ranges, and the successful/failed keyspaces/tables.
> However, on a node when repair is running, we miss a few fine-grained signals
> {*}while repair is in progress{*}, such as the following:
> # Number of tables/keyspaces/token ranges repaired vs. pending
> # Number of Merkle trees/token-ranges out of sync, which indirectly tells us
> inconsistencies among the nodes
> ## Convert this metric into % of data in sync vs. not
>
> Fine-grained node-level observability also came up while
> [reviewing|https://github.com/jaydeepkumar1984/cassandra/pull/54#issuecomment-2813945023]
> the POC for Repair on bootstrap, as it is a must for repairing as part of
> the bootstrap.
> This ticket is to improve the AutoRepair observability, and make it similar
> to _nodetool compactionstats_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
