cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Lourie (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-14363) system_distributed.repair_history is not properly updated if parent dies
Date Wed, 04 Apr 2018 04:03:00 GMT
Alex Lourie created CASSANDRA-14363:
---------------------------------------

             Summary: 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
            Reporter: Alex Lourie
             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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message