[jira] [Commented] (CASSANDRA-20013) Suggestions from masokol (from ecchronos experience)

["Jaydeepkumar Chovatia (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-20013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892559#comment-17892559 ] 

Jaydeepkumar Chovatia commented on CASSANDRA-20013:
---------------------------------------------------

As per the discussion in #cassandra-repair-scheduling-cep37, we decided to prioritize writing cross-version repair test cases and then prioritize the disabling repair during a major version upgrade. cc: [~tolbertam] [~jjordan] [~dcapwell] 

> 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] 
>  # 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org