[
https://issues.apache.org/jira/browse/CASSANDRA-14363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
C. Scott Andreas updated CASSANDRA-14363:
-----------------------------------------
Component/s: Repair
> system_distributed.repair_history is not properly updated if parent dies
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-14363
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14363
> Project: Cassandra
> Issue Type: Bug
> Components: Repair
> Reporter: Alex Lourie
> Priority: Minor
> Fix For: 4.x
>
>
> When we start a repair on a node, the information is written to
> system_distributed.repair_history. If the node running it happens to be a
> parent (the one holding the repair session) and it dies, the entries for the
> repair that was running will be stuck in "STARTED" state without being
> updated.
> To resolve this, the node should check on start whether it was a parent
> before crash/restart, and if there are entries in the table (and in
> system_distributed.parent_repair_history too), and mark those entries as
> FAILED.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
