Bianca Stanciu created CASSSIDECAR-495:
------------------------------------------
Summary: Report each instance's own Sidecar instance id in the
ring / token-range-replicas response
Key: CASSSIDECAR-495
URL: https://issues.apache.org/jira/browse/CASSSIDECAR-495
Project: Sidecar for Apache Cassandra
Issue Type: Improvement
Components: Rest API
Reporter: Bianca Stanciu
Assignee: Bianca Stanciu
*+Problem:+*
Analytics clients that talk to Sidecar behind a load balancer cannot tell which
physical Cassandra instance a request will land on. When several instances are
reachable only through one shared address (a load-balancer endpoint), the client
has no way to attach the correct per-instance routing id per request.
Two cassandra-analytics PRs work around this today, and both converge on the
same
missing server capability:
- [CASSANALYTICS-177 / apache/cassandra-analytics#222
|https://github.com/apache/cassandra-analytics/pull/222]— adds an instanceId
query
param to fix HTTP 421 routing. It can only resolve per-instance ids from
static
address-keyed config, so it fails fast (“Duplicate key” / ambiguous-config
error)
when instances share an address.
- [CASSANALYTICS-181 / apache/cassandra-analytics#223
|https://github.com/apache/cassandra-analytics/pull/223]— time-skew validation
behind
a load balancer; sidesteps per-replica addressing by querying the LB directly.
Include each replica’s own Sidecar instance id in the ring /
token-range-replicas
response, so clients can resolve routing coverage from the live ring itself
rather
than from static, address-keyed configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
