[
https://issues.apache.org/jira/browse/CASSSIDECAR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956452#comment-17956452
]
Yuntong Qu commented on CASSSIDECAR-253:
----------------------------------------
Since gossip/native start/stop are fairly quick, I didn't actually plan to
track them through `OperationalJobManager`, I assumed that the intention of
`/api/v1/cassandra/operations/` are meant for long running jobs?
1. do you think we should track gossip/native start/stop with
`OperationalJobManager`( similar to decommission)? To put it another way,
should we reserve `/api/v1/cassandra/operations/` for long running jobs that
needs tracking
2. if not, maybe below for more clarity?
`PUT /api/v1/cassandra/gossip/start`
`PUT /api/v1/cassandra/gossip/stop`
And likewise for native:
`PUT /api/v1/cassandra/native-transport/start`
`PUT /api/v1/cassandra/native-transport/stop`
> Create API to enable/disable gossip & enable/disable Native Transport via
> sidecar
> ---------------------------------------------------------------------------------
>
> Key: CASSSIDECAR-253
> URL: https://issues.apache.org/jira/browse/CASSSIDECAR-253
> Project: Sidecar for Apache Cassandra
> Issue Type: New Feature
> Components: Rest API
> Reporter: Yuntong Qu
> Assignee: Yuntong Qu
> Priority: Normal
> Fix For: 0.2
>
>
> Currently we can enable/disable gossip & enable/disable Native Transport via
> nodetool. This can be useful for traffic shaping and quarantine misbehaving
> nodes.
> We would like to create APIs to enable/disable gossip & enable/disable Native
> Transport in sidecar, to more easily intergrate with automated control planes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
