[
https://issues.apache.org/jira/browse/CASSJAVA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17982744#comment-17982744
]
Abe Ratnofsky commented on CASSJAVA-92:
---------------------------------------
> I would put there more information than less. All local dc, dc-failover,
> execution profile it is connecting with ...
This is the point I'm trying to get at. We might as well push the entire
basic.load-balancing-policy and advanced.load-balancing-policy configurations,
so context on dc-failover is included. Let's say we call it DRIVER_BAGGAGE (to
borrow the OpenTelemetry terminology) and JSON-encode fields, so Startup
options looks something like:
{code:json}
{"DRIVER_BAGGAGE": "{\"default\": {\"LoadBalancingPolicies\": {\"default\":
\"BasicLoadBalancingPolicy{localDc=dc0, preferredRemoteDcs=Set{dc1},
maxNodesPerRemoteDc=3, ...}\"}}]}}"}
{code}
> Add Local DC to driver connection info and provide visibility with nodetool
> clientstats
> ---------------------------------------------------------------------------------------
>
> Key: CASSJAVA-92
> URL: https://issues.apache.org/jira/browse/CASSJAVA-92
> Project: Apache Cassandra Java driver
> Issue Type: Improvement
> Components: Core
> Reporter: Brad Schoening
> Assignee: Lukasz Antoniak
> Priority: Normal
> Fix For: 4.19.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> When a client application connects to Cassandra using one of the drivers, it
> specifies a local DC now. If the server is aware of the local DC specified,
> this would be very useful to include in {_}nodetool clientstats{_}.
> We often have clusters running disaster recovery scenarios and they'll turn
> off NTR on a DC. But they do not always understand what DC's are being used
> as local DC if they have dozens of applications connecting from different
> teams. In a brown-out scenario, this would also be useful to identify the
> applications connecting to a degraded datacenter.
--
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
