[
https://issues.apache.org/jira/browse/CASSJAVA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945315#comment-17945315
]
Lukasz Antoniak commented on CASSJAVA-92:
-----------------------------------------
Instead of map, can we send a comma separated list of DCs? From _nodetool_
perspective, we would say that this is a list of potential DCs that client may
want to connect to. It just feels bad for me that we are impacting the way we
send data by Java driver internals (other drivers do not support profiles).
> 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
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
