[
https://issues.apache.org/jira/browse/CASSSIDECAR-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016849#comment-18016849
]
Arjun Ashok commented on CASSSIDECAR-274:
-----------------------------------------
Thanks for clarifying the point about the difference between Sidecar and
Cassandra operations.
My perspective is based on the user experience of the Sidecar as a control
plane for cluster management, which to be effective, should provide a single,
cohesive mechanism for managing all long-running operations regardless of the
operation's scope.
I think extending the job-management framework has the advantage of reducing
client complexity by offering a consistent, discoverable API that is enabled by
centralized state management. A prerequisite for this is a durable,
cluster-accessible state for jobs, allowing any node to query the status of any
job (Tracked by a ticket I recently created:
https://issues.apache.org/jira/browse/CASSSIDECAR-341).
Is there a particular benefit (or limitation with the existing framework) to
keeping these operation types distinct at the API level that I might be missing?
> Enable rolling restarts of Cassandra clusters via Sidecar
> ---------------------------------------------------------
>
> Key: CASSSIDECAR-274
> URL: https://issues.apache.org/jira/browse/CASSSIDECAR-274
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Reporter: Isaac Reath
> Priority: Major
> Attachments: Screenshot 2025-08-13 at 12.34.43 PM.png
>
>
> Rolling restarts are frequently used in Cassandra to apply changes to a
> cluster such as configuration changes, or version upgrades. In
> CASSSIDECAR-266, we are adding functionality to safely start and stop a
> single Cassandra node via Sidecar. This ticket will build on that work to
> implement a coordinated rolling restart.
> The scope of this effort includes:
> * Adding API endpoints to enable operators to start, monitor, pause and stop
> a rolling restart.
> * Updating Sidecar to orchestrate start and stop operations across the
> cluster, allowing for a configurable amount of nodes to be offline
> simultaneously.
> * Creating safeguards to ensure that a rolling restart is safe to perform
> and does not interfere with other operations ongoing in the cluster such as
> node bootstraps or decommissions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
