[ https://issues.apache.org/jira/browse/CASSANDRA-11801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-11801: ----------------------------------------- Component/s: Lifecycle Distributed Metadata > 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: Distributed Metadata, Lifecycle > Reporter: Tyler Hobbs > Priority: Major > > 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 (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org