[
https://issues.apache.org/jira/browse/CASSJAVA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965485#comment-17965485
]
Stefan Miklosovic edited comment on CASSJAVA-92 at 6/12/25 7:41 AM:
--------------------------------------------------------------------
One small caveat to that is that users should understand that whatever they put
into that map will be visible in nodetool clientstats --verbose (I hope I got
that flag right) and if they put there something security sensitive,
credentials of any kind or anything like that, it will be most probably on
them. However I do not think that the risk of exposing something like that is
big.
For now it is only us / driver's developers who have under control what will
appear in that map. It is not like an ordinary user has any say what goes there.
to 2) well, since we can put whatever into that map, theoretically, then we can
put here also what load balancing policy a client uses with that failover
config etc.? Together with execution profile and DC etc. Basically whatever we
want?
I would put there more information than less. All local dc, dc-failover,
execution profile it is connecting with ...
was (Author: smiklosovic):
One small caveat to that is that users should understand that whatever they put
into that map will be visible in nodetool clientstats --verbose (I hope I got
that flag right) and if they put there something security sensitive,
credentials of any kind or anything like that, it will be most probably on
them. However I do not think that the risk of exposing something like that is
big.
to 2) well, since we can put whatever into that map, theoretically, then we can
put here also what load balancing policy a client uses with that failover
config etc.? Together with execution profile and DC etc. Basically whatever we
want?
I would put there more information than less. All local dc, dc-failover,
execution profile it is connecting with ...
> 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
