cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dinesh Joshi (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-14275) Cassandra Driver should send identification information to Server
Date Tue, 27 Feb 2018 23:33:00 GMT


Dinesh Joshi updated CASSANDRA-14275:
    Fix Version/s:     (was: 3.11.x)
                       (was: 3.0.x)
                       (was: 2.2.x)
                       (was: 2.1.x)

> Cassandra Driver should send identification information to Server
> -----------------------------------------------------------------
>                 Key: CASSANDRA-14275
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Dinesh Joshi
>            Assignee: Dinesh Joshi
>            Priority: Major
>             Fix For: 4.x
> Currently there doesn't seem to be any way to readily identify the driver that clients
are using to connect to Cassandra. Add the capability of identifying the driver through metadata
information much like how HTTP Clients identify themselves through User-Agent HTTP header.
This is useful for debugging in large deployments where clients tend to use different drivers,
wrappers and language bindings to connect to Cassandra. This can help surface issues as well
as help detect clients which are using older or unsupported drivers.
> The identification information should be a string that unambiguously identifies the driver.
It should include information such as the name of the driver, it's version, CQL version, Platform
(Linux, macOS, Windows, etc.) and architecture (x86, x86_64).
> We should surface this information in `nodetool clientstats` command.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message