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 2026/04/10 22:00:00 UTC
[jira] [Moved] (CASSSIDECAR-425) CEP-62: Cassandra Configuration Management via Sidecar
[ https://issues.apache.org/jira/browse/CASSSIDECAR-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paulo Motta moved CASSANDRA-21297 to CASSSIDECAR-425:
-----------------------------------------------------
Impacts: (was: None)
Key: CASSSIDECAR-425 (was: CASSANDRA-21297)
Platform: (was: All)
Project: Sidecar for Apache Cassandra (was: Apache Cassandra)
> CEP-62: Cassandra Configuration Management via Sidecar
> ------------------------------------------------------
>
> Key: CASSSIDECAR-425
> URL: https://issues.apache.org/jira/browse/CASSSIDECAR-425
> Project: Sidecar for Apache Cassandra
> Issue Type: Epic
> Reporter: Paulo Motta
> Priority: Normal
>
> Implement configuration management in Cassandra Sidecar to enable programmatic control over cassandra.yaml and JVM options through a REST API.
> The module introduces a REST API (GET, PATCH) backed by a Configuration Manager that maintains per-instance configuration on disk. Operators define base templates in sidecar.yaml and apply instance-specific customizations as overlays through the PATCH endpoint. The manager merges these layers, validates the result against a JSON Schema tied to the instance's Cassandra version, and materializes the final cassandra.yaml and extra JVM options files in the local configuration store. When an instance is started through the lifecycle API, the LifecycleProvider loads these artifacts automatically.
> Overlay storage is pluggable via a ConfigurationProvider interface. The default provider stores overlays as local JSON files, but operators can swap in external backends. Failure policies control behavior when the provider is unreachable, and optimistic concurrency via content hashing prevents conflicting updates.
> Key deliverables:
> * Configuration REST API (GET, PATCH)
> * Configuration Manager with version-aware validation and overlay merging
> * On-disk Configuration Store with per-instance artifacts
> * Pluggable ConfigurationProvider interface with default local implementation
> * Lifecycle Provider integration to apply managed configuration on startup
> * Optimistic concurrency control via SHA-256 hashing
> * Immutable settings blocklist and failure policy enforcement
> * JSON Schema generation per supported Cassandra major version
> Reference: [CEP-62|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-62%3A+Cassandra+Configuration+Management+via+Sidecar]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org