[
https://issues.apache.org/jira/browse/CASSANDRASC-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090807#comment-17090807
]
Jon Haddad commented on CASSANDRASC-17:
---------------------------------------
I'll be honest, I'm not wild about batch requests to multiple nodes, and I'd
prefer to punt on it at least for now. There's a whole bunch of weirdness
around bulk requests like that (similar to batch statements in C*). I'd like
to put some thought into the semantics of /all/ behavior. I don't expect this
to be a commonly used feature to begin with, so for the very few teams using
1:N sidecar Cassandra nodes are probably better off sending 4 requests for 4 C*
instances since each one has its own timeout and retry behavior.
> 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]
