[
https://issues.apache.org/jira/browse/CASSSIDECAR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955924#comment-17955924
]
Yuntong Qu commented on CASSSIDECAR-253:
----------------------------------------
Thank you all for responding. I added “enable/disable CQL” to Sidecar locally
and was able to:
# Connect to C*, then disable CQL on an instance and later re-enable it.
# Start the C* instance with CQL disabled, then enable CQL through Sidecar.
During those times, Sidecar behaved normally.
Some operations—like getting the schema (through CQL)—still worked if Sidecar
had previously connected to the instance via CQL and then disconnected. That’s
because the schema is periodically reported to Sidecar, rather than fetched
live.
> are not there some management operations in Sidecar itself working via CQL
> which are vital to Sidecar's functionality?
I’m not sure, but since we can always re-enable CQL through Sidecar, I don’t
foresee this being a problem.
> 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]
