You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Blake Eggleston (JIRA)" <ji...@apache.org> on 2018/12/17 21:54:00 UTC
[jira] [Created] (CASSANDRA-14939) fix some operational holes in
incremental repair
Blake Eggleston created CASSANDRA-14939:
-------------------------------------------
Summary: 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
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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org