You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Paulo Motta (Jira)" <ji...@apache.org> on 2021/02/15 22:05:00 UTC
[jira] [Updated] (CASSANDRA-11801) Add ability to disable schema
changes, repairs, bootstraps, etc (during upgrades)
[ https://issues.apache.org/jira/browse/CASSANDRA-11801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paulo Motta updated CASSANDRA-11801:
------------------------------------
Labels: gsoc2021 mentor (was: )
> Add ability to disable schema changes, repairs, bootstraps, etc (during upgrades)
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-11801
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11801
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Distributed Metadata, Local/Startup and Shutdown
> Reporter: Tom Hobbs
> Priority: Normal
> Labels: gsoc2021, mentor
>
> There are a lot of operations that aren't supposed to be run in a mixed version cluster: schema changes, repairs, topology changes, etc. However, it's easily possible for these operations to be accidentally run by a script, another user unaware of the upgrade, or an operator that's not aware of these rules.
> We should make it easy to follow the rules by making it possible to prevent/disable all of these operations through nodetool commands. At the start of an upgrade, an operator can disable all of these until the upgrade has been completed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org