cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Deleted] (CASSANDRA-11802) Add ability to disable schema changes, repairs, bootstraps, etc (during upgrades)
Date Fri, 13 May 2016 18:52:13 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tyler Hobbs deleted CASSANDRA-11802:
------------------------------------


> Add ability to disable schema changes, repairs, bootstraps, etc (during upgrades)
> ---------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-11802
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11802
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Tyler Hobbs
>
> 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
(v6.3.4#6332)

Mime
View raw message