[
https://issues.apache.org/jira/browse/CASSANDRA-20013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893570#comment-17893570
]
Jaydeepkumar Chovatia commented on CASSANDRA-20013:
---------------------------------------------------
There is also a suggestion from [~mck] to support priority/schedule at the
table level followed by the DC level. This needs to be considered as well.
> Suggestions from masokol (from ecchronos experience)
> ----------------------------------------------------
>
> Key: CASSANDRA-20013
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20013
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Repair
> Reporter: Jaydeepkumar Chovatia
> Assignee: Jaydeepkumar Chovatia
> Priority: Normal
>
> Here are a few changes suggested by [~masokol]
> # Repair: Write x-version repair test cases to ensure the repair does not
> break while upgrading
> # Major versions: During major version upgrades like 3 -> 4, we weren't
> supposed to run repairs. If Cassandra plans to keep this, then it would be
> nice for repairs to automatically pause during major version upgrades.
> # Repair priority per table, not per node.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
