pauloricardomg opened a new pull request, #4560:
URL: https://github.com/apache/cassandra/pull/4560

   When a node crashes during its first auto-repair, the repair was incorrectly 
skipped by the "too soon" check after restart. This happened because 
tooSoonToRunRepair() uses repair_finish_ts which was set to the record creation 
time, not when repair actually finished. The in-progress detection logic in 
myTurnToRunRepair() was never reached.
   
   The fix adds an in-progress check within tooSoonToRunRepair() that detects 
when repair_start_ts > repair_finish_ts and allows the repair to resume.
   
   Patch by Paulo Motta; reviewed by X for CASSANDRA-21115
   
   Thanks for sending a pull request! Here are some tips if you're new here:
    
    * Ensure you have added or run the [appropriate 
tests](https://cassandra.apache.org/_/development/testing.html) for your PR.
    * Be sure to keep the PR description updated to reflect all changes.
    * Write your PR title to summarize what this PR proposes.
    * If possible, provide a concise example to reproduce the issue for a 
faster review.
    * Read our [contributor 
guidelines](https://cassandra.apache.org/_/development/index.html)
    * If you're making a documentation change, see our [guide to documentation 
contribution](https://cassandra.apache.org/_/development/documentation.html)
    
   Commit messages should follow the following format:
   
   ```
   <One sentence description, usually Jira title or CHANGES.txt summary>
   
   <Optional lengthier description (context on patch)>
   
   patch by <Authors>; reviewed by <Reviewers> for CASSANDRA-#####
   
   Co-authored-by: Name1 <email1>
   Co-authored-by: Name2 <email2>
   
   ```
   
   The [Cassandra 
Jira](https://issues.apache.org/jira/projects/CASSANDRA/issues/)
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to