[
https://issues.apache.org/jira/browse/CASSANDRA-14939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105790#comment-17105790
]
Jordan West commented on CASSANDRA-14939:
-----------------------------------------
[~kohlisankalp] I don't personally have enough background to comment on this
ticket. With fresh eyes I saw it as a potential candidate for a follow up
release since it hasn't been worked on for over one year and looks to be a set
of improvements on an existing feature. I defer to those involved with the
ticket and/or the community if its better to start a conversation on the
mailing list.
> 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: [email protected]
For additional commands, e-mail: [email protected]
