[jira] [Comment Edited] (CASSJAVA-92) Add Local DC to driver connection info and provide visibility with nodetool clientstats

["Stefan Miklosovic (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSJAVA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955888#comment-17955888 ] 

Stefan Miklosovic edited comment on CASSJAVA-92 at 6/3/25 12:55 PM:
--------------------------------------------------------------------

[~aratnofsky] by the way there is already `CLIENT_OPTIONS` in `ClientsTable` and it is all shown in ClientStats as well (nodetool clientstats) with --verbose or --client-options specified. That is already a map. Can you use that instead? I would keep driver local dc separate as done in CASSANDRA-20694.

Or you want to have a dedicated map just for driver-related options? Why could not we reuse options already available instead? If your aim is to not mix driver's options together with more general options map that is understandable.


was (Author: smiklosovic):
[~aratnofsky] by the way there is already `CLIENT_OPTIONS` in `ClientsTable` and it is all shown in ClientStats as well (nodetool clientstats) with --verbose or --client-options specified. That is already a map. Can you use that instead? I would keep driver local dc separate as done in CASSANDRA-20694.

> 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: 1h
>  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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org