[
https://issues.apache.org/jira/browse/CASSJAVA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955926#comment-17955926
]
Stefan Miklosovic commented on CASSJAVA-92:
-------------------------------------------
We can indeed shove it all under client's stats and be done with it. That would
render my PR redundant which is ideal :) However, we already do have separate
driverName and driverVersion so I was thinking that having driverLocalDc is
just a natural continuation of that but if you are OK with putting additional
driver options under client options that is just fine.
> 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: [email protected]
For additional commands, e-mail: [email protected]
