[
https://issues.apache.org/jira/browse/CASSANDRA-7530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630993#comment-17630993
]
Michael Semb Wever commented on CASSANDRA-7530:
-----------------------------------------------
Note, the new Messaging System (4.0) [does
not|https://issues.apache.org/jira/browse/CASSANDRA-15066?focusedCommentId=16801284&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16801284]
support mix-version (by [MS
versions|https://github.com/apache/cassandra/blob/cassandra-4.0/src/java/org/apache/cassandra/net/MessagingService.java#L201])
streaming
[anymore|https://github.com/apache/cassandra/blob/cassandra-4.0/src/java/org/apache/cassandra/net/InboundConnectionInitiator.java#L298-L305].
> Repair should be allowed in mixed version clusters
> --------------------------------------------------
>
> Key: CASSANDRA-7530
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7530
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Repair
> Reporter: Jeremiah Jordan
> Priority: Normal
> Labels: ponies
>
> As we try to improve the ops experience for large clusters (or cautious
> people), we need to make it so repair works across major version upgrades.
> Currently you have to be able to upgrade all of your nodes and then run a
> full repair, within the gc_grace window.
> The recent ability to stream old sstables makes this a little better, as you
> don't have to also run upgradesstables first.
> It would be really good if we could let people pause their upgrade of 1000
> nodes to run some repairs. Or to upgrade one DC and test the new major
> version for a while (while still running repairs).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
