[
https://issues.apache.org/jira/browse/CASSSIDECAR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrés Beck-Ruiz updated CASSSIDECAR-376:
-----------------------------------------
Description:
The {{OperationalJob}} abstract class should be enhanced with new fields to
support cluster wide operations and give operators proper visibility into the
status of these operations. The following fields should be added (discussed in
more detail [here in
CEP-53|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=382175762#CEP53:CassandraRollingRestartsviaSidecar-NewOperationalJobObject])
* {{startTime String}}
* {{operationType String}}
* {{nodesPending List<UUID>}}
* {{nodesExecuting List<UUID>}}
* {{nodesSucceeded List<UUID>}}
* {{nodesFailed List<UUID>}}
* {{lastUpdate String}}
We also need to ensure these fields are backwards compatible for single node
jobs. For example, a client should be able to create a local
{{DecommissionJob}} on a single node with the old POST request, but new fields
will be returned.
We should also update the {{OperationalJobStatus}} enum to support {{PAUSED}}
and {{ABORTED}} statuses, enabling more operator control over cluster-wide
operations.
was:
The {{OperationalJob}} abstract class should be enhanced with new fields to
support cluster wide operations and give operators proper visibility into the
status of these operations. The following fields should be added (discussed in
more detail [here in
CEP-53|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=382175762#CEP53:CassandraRollingRestartsviaSidecar-NewOperationalJobObject])
* {{startTime String}}
* {{operationType String}}
* {{nodesPending List<UUID>}}
* {{nodesExecuting List<UUID>}}
* {{nodesSucceeded List<UUID>}}
* {{nodesFailed List<UUID>}}
* {{lastUpdate String}}
We also need to ensure these fields are backwards compatible for single node
jobs. For example, a client should be able to create a local
{{DecommissionJob}} on a single node with the old POST request, but new fields
will be returned.
We should also update the {{OperationalJobStatus}} enum to support {{PAUSED}}
and {{ABORTED}} statuses, enabling more operator control over cluster-wide
operations.
> Update OperationalJob class to support cluster-wide operations
> --------------------------------------------------------------
>
> Key: CASSSIDECAR-376
> URL: https://issues.apache.org/jira/browse/CASSSIDECAR-376
> Project: Sidecar for Apache Cassandra
> Issue Type: Sub-task
> Reporter: Andrés Beck-Ruiz
> Priority: Major
>
> The {{OperationalJob}} abstract class should be enhanced with new fields to
> support cluster wide operations and give operators proper visibility into the
> status of these operations. The following fields should be added (discussed
> in more detail [here in
> CEP-53|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=382175762#CEP53:CassandraRollingRestartsviaSidecar-NewOperationalJobObject])
> * {{startTime String}}
> * {{operationType String}}
> * {{nodesPending List<UUID>}}
> * {{nodesExecuting List<UUID>}}
> * {{nodesSucceeded List<UUID>}}
> * {{nodesFailed List<UUID>}}
> * {{lastUpdate String}}
>
> We also need to ensure these fields are backwards compatible for single node
> jobs. For example, a client should be able to create a local
> {{DecommissionJob}} on a single node with the old POST request, but new
> fields will be returned.
> We should also update the {{OperationalJobStatus}} enum to support {{PAUSED}}
> and {{ABORTED}} statuses, enabling more operator control over cluster-wide
> operations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
