[ 
https://issues.apache.org/jira/browse/CASSJAVA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955954#comment-17955954
 ] 

Abe Ratnofsky commented on CASSJAVA-92:
---------------------------------------

I wouldn't want to change how it works for DRIVER_NAME and DRIVER_VERSION, but 
for new fields, particularly optional / informational fields, putting them in 
ClientState.clientOptions feels right to me.

I also don't think we need to require drivers abide by specific conventions, 
like using the LOCAL_DC key. Maybe we should designate a prefix like CUSTOM_, 
so gocql for example could send CUSTOM_HOST_SELECTION_POLICY = 
"gocql.TokenAwareHostPolicy(gocql.DCAwareRoundRobinPolicy("dc1"))".

> 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: 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

Reply via email to