[jira] [Commented] (CASSANDRA-15399) Add ability to track state in repair

["David Capwell (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-15399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969477#comment-16969477 ] 

David Capwell commented on CASSANDRA-15399:
-------------------------------------------

I created a PR to get early feedback, but the code is not ready for merge at all (needs to be cleaned up, and go through a lot more testing).

This provides two new virtual tables: repairs, and repair_validations.

repairs is called on the coordinator and provides a unified view of the coordinator and participant's state.  I added new verbs VALIDATION_STATUS_REQ and VALIDATION_STATUS_RSP to allow this table to get access to the validation in-flight (later coordinator could use this to make sure validations are running and making progress).

repair_validations runs on the participants and shows the progress of the validation task; this table is similar to 
{code:java}
nodetool compactionstats
{code}

Open Issues:
* if a validation is detected on a host, be able to backtrack to the coordinator
* sync progress is not tracked, desirable to have repair_sync table once that is done

> Add ability to track state in repair
> ------------------------------------
>
>                 Key: CASSANDRA-15399
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15399
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Consistency/Repair
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> To enhance the visibility in repair, we should add in-memory objects that can be exposed via JMX and virtual tables to show the state of the coordinator, and validations (leaving sync out for now).
> These objects should expose the timing (create, start, complete), current state (enum specific to the entity), and progress estimate (% complete); along with any entity specific information useful.
> To help with growth, ActiveRepairService should periodically cleanup completed state after a configurable interval.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org