[
https://issues.apache.org/jira/browse/CASSJAVA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960568#comment-17960568
]
Abe Ratnofsky commented on CASSJAVA-92:
---------------------------------------
There are two components here I want to discuss:
1. Clients passing arbitrary session context to the server for generic
investigations
2. Adding context in nodetool clientstats for failover activities,
[~bschoeni]'s motivation in the original description
For #1, I think we're all on the same page, it's useful to have all kinds of
context for investigations, we'll probably expand this list with compression,
rack, session name, etc. This context is expected to be read by humans, doesn't
require conventions on field names, etc. We should expect to add new fields
here without requiring changes on the server.
For #2 - is it sufficient to check connected clients' local DC when deciding
whether to turn off native transport for a given node? What we really want to
check is whether a client has enough connections to other nodes. If a client
uses advanced.load-balancing-policy.dc-failover, it's safe to turn off the
local DC, but we don't get that information from the patch as it exists now.
> 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
