[
https://issues.apache.org/jira/browse/CASSJAVA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944646#comment-17944646
]
Stefan Miklosovic edited comment on CASSJAVA-92 at 4/15/25 7:54 AM:
--------------------------------------------------------------------
I can't answer this from Java Driver perspective as my knowledge in all the
details in there is pretty limited but from server's point of view, all I am
looking at is "options" in StartupMessage. We already process keys / values
driver is supposed to put there and we just skip when it is not there so the
same treatment would be applied here. When I do not see any "DRIVER_LOCAL_DC",
it is just ignored and a user sees "null" in client's tables etc.
Whatever you guys agree on to send over I am prepared to digest one way or
another, however, in general, you should send us DRIVER_LOCAL_DC in case it
actually makes a difference. If it is not effectively used because of a
different LBP used as described above, there is no point in making
DRIVER_LOCAL_DC visible on server's side when it does nothing. It would just
confuse people.
was (Author: smiklosovic):
I can't answer this from Java Driver perspective as my knowledge in all the
details in there is pretty limited but from server's point of view, all I am
looking at is "options" in StartupMessage. We already process keys / values
driver is supposed to put there and we just skip when it is not there so the
same treatment would be applied here. When I do not see any "DRIVER_LOCAL_DC",
it is just ignored and a user sees "null" in client's tables etc.
Whatever you guys agree on to send over I am prepared to digest one way or
another, however, in general, you should send us DRIVER_LOCAL_DC in case it
actually makes a difference. If it is not effectively used because of a
different LBP used as described above, there is not point in making
DRIVER_LOCAL_DC visible on server's side when it does nothing. It would just
confuse people.
> 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: 40m
> 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]
