[
https://issues.apache.org/jira/browse/CASSANDRA-21169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-21169:
------------------------------------
Change Category: Operability
Complexity: Normal
Component/s: Local/Compaction
Status: Open (was: Triage Needed)
> Allow overriding compaction strategy parameters during startup
> --------------------------------------------------------------
>
> Key: CASSANDRA-21169
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21169
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Local/Compaction
> Reporter: Paulo Motta
> Assignee: Paulo Motta
> Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> One strategy to perform large scale compaction strategy changes is to perform
> the change on a per-node, per-rack or per-dc basis via JMX to control the
> impact in the cluster.
> However if nodes that have change their compaction via JMX are restarted
> before the schema is updated, the old compaction parameters are restored from
> the schema causing lost work.
> This ticket is to add a new configuration to override parameters of specific
> table or keyspacesat startup via the following JVM properties:
> - cassandra.override_compaction.entities: comma-separated list of keyspaces
> and keyspace.table pairs (e.g. "ks1,ks2.tbl1,ks3.tbl2")
> - cassandra.override_compaction.params: JSON compaction parameters to apply
> When these properties are set, the schema compaction parameters are ignored
> for the specified entities and the specified parameters are used instead to
> initialize compaction.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
