[CASSANDRA-14939] fix some operational holes in incremental repair

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0
• Severity: Normal
• Complexity: Normal
• Since Version: 4.0-alpha1

Source Control Link

https://github.com/apache/cassandra/commit/c34317526fc6dbe559beb36cf44e24278656bdf2

• Assignee: Blake Eggleston
• Reporter: Blake Eggleston

Authors

Blake Eggleston

Reviewers

Marcus Eriksson

• Created: 17/Dec/18 21:53
• Updated: 09/Oct/20 20:04
• Resolved: 25/Aug/20 22:30

Description

Incremental repair has a few operational rough spots that make it more difficult to fully automate and operate at scale than it should be.

• Visibility into whether pending repair data exists for a given token range.
• Ability to force promotion/demotion of data for completed sessions instead of waiting for compaction.
• Get the most recent repairedAt timestamp for a given token range.