[jira] [Commented] (CASSANDRA-15564) Refactor repair coordinator so errors are consistent

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

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

David Capwell commented on CASSANDRA-15564:
-------------------------------------------

I am going to rebase now that CASSANDRA-15553 is merged. 

[~ifesdjeen] that JIRA enabled IR in dtests without the feature flag; and I personally agree with that, so once I rebase it won't show up in the diff.

> Refactor repair coordinator so errors are consistent
> ----------------------------------------------------
>
>                 Key: CASSANDRA-15564
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15564
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Consistency/Repair
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>              Labels: pull-request-available
>          Time Spent: 11h 10m
>  Remaining Estimate: 0h
>
> This is to split the change in CASSANDRA-15399 so the refactor is isolated out.
> Currently the repair coordinator special cases the exit cases at each call site; this makes it so that errors can be inconsistent and there are cases where proper complete isn't done (proper notifications, and forgetting to update ActiveRepairService).
> [Circle CI|https://circleci.com/gh/dcapwell/cassandra/tree/bug%2FrepairCoordinatorJmxConsistency]



--
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