[
https://issues.apache.org/jira/browse/CASSSIDECAR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956469#comment-17956469
]
Arjun Ashok commented on CASSSIDECAR-253:
-----------------------------------------
Hi Yuntong,
1. Correct. We do not need `OperationalJobManager` integration for these
endpoints, as they are short-lived.
> should we reserve `/api/v1/cassandra/operations/` for long running jobs that
> needs tracking
I will propose a guidelines doc for Sidecar endpoints clarifying this, after
giving it more thought and getting inputs from other committers.
2. It would be beneficial here to be RESTful here (without the verb in the
URI), so on further thought, we should be doing something like this:
This is consistent with the existent `gossip` and `native` resources in Sidecar
(used for health-checks).
{quote}
PUT /api/v1/cassandra/gossip
{
"state": "<stop|start>"
}
PUT /api/v1/cassandra/native
{
"state": "<stop|start>"
}
{quote}
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
