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

["Brad Schoening (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSJAVA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brad Schoening updated CASSJAVA-92:
-----------------------------------
    Change Category: Operability
         Complexity: Low Hanging Fruit
        Component/s: Core
             Status: Open  (was: Triage Needed)

> 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
>            Priority: Normal
>
> 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