[
https://issues.apache.org/jira/browse/CASSANDRASC-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Haddad updated CASSANDRASC-17:
----------------------------------
Resolution: Won't Fix
Status: Resolved (was: Triage Needed)
I'm going to close this out since I don't plan on implementing it and I'm not
sure if it's worth it anymore.
> Ensure sidecar can control multiple Cassandra instances
> -------------------------------------------------------
>
> Key: CASSANDRASC-17
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-17
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
> Reporter: Jon Haddad
> Priority: Normal
>
> Since we can run multiple hosts per node, we should allow a single sidecar
> process to control multiple Cassandra nodes.
> I am not sure if we should encode the id of the node in the URL or as a
> parameter that would have to be present in every request if using > 1 node.
> I lean towards the latter - meaning it’s a slight inconvenience for a very
> small group, rather than messing with the URL scheme for everyone else. I
> don’t hold this opinion very strongly though. I’d like to discuss before
> doing any work here.
> Thoughts?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
