[
https://issues.apache.org/jira/browse/CASSANDRA-14939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-14939:
----------------------------------------
Since Version: 4.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/c34317526fc6dbe559beb36cf44e24278656bdf2
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed to trunk as [c34317526fc6dbe559beb36cf44e24278656bdf2
|https://github.com/apache/cassandra/commit/c34317526fc6dbe559beb36cf44e24278656bdf2],
thanks!
> fix some operational holes in incremental repair
> ------------------------------------------------
>
> Key: CASSANDRA-14939
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14939
> Project: Cassandra
> Issue Type: Bug
> Reporter: Blake Eggleston
> Assignee: Blake Eggleston
> Priority: Normal
> Fix For: 4.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
