[
https://issues.apache.org/jira/browse/CASSJAVA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17966246#comment-17966246
]
Brad Schoening edited comment on CASSJAVA-92 at 6/12/25 1:30 PM:
-----------------------------------------------------------------
Regarding [~aratnofsky] issue #2, having local DC visible will be quite a help.
It's quite right that it doesn't show all the details of the policy, such as
using remote DC nodes for local quorum and how many. But, showing local DC
alone will be great.
was (Author: bschoeni):
Regarding [~aratnofsky] issue #2, having local DC visible will be quite a help.
It's quite right that it doesn't show all the details of the policy, such as
using remote DC nodes for local quorum and how many. But, making local DC
visible will be great.
> 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
