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/06/18 22:31:00 UTC

[jira] [Updated] (CASSSIDECAR-440) Integrate ProcessLifecycleProvider with Configuration Manager

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

Paulo Motta updated CASSSIDECAR-440:
------------------------------------
    Change Category: Semantic
         Complexity: Normal
        Component/s: Configuration
           Assignee: Paulo Motta
             Status: Open  (was: Triage Needed)

> Integrate ProcessLifecycleProvider with Configuration Manager
> -------------------------------------------------------------
>
>                 Key: CASSSIDECAR-440
>                 URL: https://issues.apache.org/jira/browse/CASSSIDECAR-440
>             Project: Sidecar for Apache Cassandra
>          Issue Type: Task
>          Components: Configuration
>            Reporter: Paulo Motta
>            Assignee: Paulo Motta
>            Priority: Major
>
> When configuration management is enabled, the lifecycle start flow must ensure the latest configuration is applied before starting Cassandra. On a start request, the \{{LifecycleManager}} calls the Configuration Manager to refresh the effective configuration (fetching the latest overlay from the \{{ConfigurationProvider}} and rematerializing artifacts). The \{{ProcessLifecycleProvider}} then copies the materialized \{{cassandra.yaml}} from the configuration store to \{{$CASSANDRA_CONF}} and appends \{{extraJvmOpts}} to the JVM startup command before launching the Cassandra process.
> Acceptance Criteria:
> - \{{LifecycleManager}} triggers a configuration refresh via the Configuration Manager before starting Cassandra.
> - \{{ProcessLifecycleProvider}} copies the materialized \{{cassandra.yaml}} from the configuration store to \{{$CASSANDRA_CONF}}.
> - \{{ProcessLifecycleProvider}} appends \{{extraJvmOpts}} entries to the JVM startup command.
> - Materialized artifacts always reflect the latest state from the base template and provider overlay.
> - Integration is only active when configuration management is enabled.



--
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