[
https://issues.apache.org/jira/browse/CASSJAVA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944648#comment-17944648
]
Stefan Miklosovic edited comment on CASSJAVA-92 at 4/15/25 8:06 AM:
--------------------------------------------------------------------
I think that there is also a _default execution profile_, right? So in that
case, looking into the link Bret sent, you might send us some kind of a map.
{code}
"default: {dc1}, oltp: {dc1,dc2}, olap: {dc3}"
{code}
This string would be visible. But again, all the dc's specified would be in
there _only in case they are actually used_.
Next question is - is Java Driver the only driver which can do this? What about
Go driver? Is there some notion of "local dc" which would be advertised as
well. If Go driver do not have "profiles", how is this going to be treated? I
think that in that case there would be just "default" all the time, even though
Go is profile-unaware.
was (Author: smiklosovic):
I think that there is also a _default execution profile_, right? So in that
case, looking into the link Bret sent, you might send us some kind of a map.
{code}
"default: {dc1}, oltp: {dc1,dc2}, olap: {dc3}"
{code}
This string would be visible. But again, all the dc's specified would be in
there _only in case they are actually used_.
> 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]
