nodetool clientstats

Return details about connected clients.

Synopsis

nodetool [<connection_options>] clientstats

Syntax legend

Syntax conventions Description

Syntax conventions	Description
Italic, bold, or `< >`	Syntax diagrams and code samples use one or more of these styles to mark placeholders for variable values. Replace placeholders with a valid option or your own user-defined value. In CQL statements, angle brackets are required to enclose data types in a set, list, map, or tuple. Separate the data types with a comma. For example: `<datatype2` In Search CQL statements, angle brackets are used to identify the entity and literal value to overwrite the XML element in the schema and `solrconfig` files, such as `@<xml_entity>='<xml_entity_type>'`.
`[ ]`	Square brackets surround optional command arguments. Do not type the square brackets.
`( )`	Parentheses identify a group to choose from. Do not type the parentheses.
`\|`	A pipe separates alternative elements. Type any one of the elements. Do not type the pipe.
`...`	Indicates that you can repeat the syntax element as often as required.
`'`	Single quotation marks must surround literal strings in CQL statements. Use single quotation marks to preserve upper case. + For Search CQL only: Single quotation marks surround an entire XML schema declaration, such as `'<<schema> ... </schema>>'`
`{ }`	Map collection. Curly braces enclose maps (`{ <key_datatype>:<value_datatype> }`) or key value pairs (`{ <key>:<value> }`). A colon separates the key and the value.
`;`	Ends a CQL statement.
`--`	Separate command line options from command arguments with two hyphens. This syntax is useful when arguments might be mistaken for command line options.

Italic, bold, or < >

Syntax diagrams and code samples use one or more of these styles to mark placeholders for variable values. Replace placeholders with a valid option or your own user-defined value.

In CQL statements, angle brackets are required to enclose data types in a set, list, map, or tuple. Separate the data types with a comma. For example: <datatype2

In Search CQL statements, angle brackets are used to identify the entity and literal value to overwrite the XML element in the schema and solrconfig files, such as @<xml_entity>='<xml_entity_type>'.

[ ]

Square brackets surround optional command arguments. Do not type the square brackets.

( )

Parentheses identify a group to choose from. Do not type the parentheses.

|

A pipe separates alternative elements. Type any one of the elements. Do not type the pipe.

...

Indicates that you can repeat the syntax element as often as required.

'

Single quotation marks must surround literal strings in CQL statements. Use single quotation marks to preserve upper case. + For Search CQL only: Single quotation marks surround an entire XML schema declaration, such as '<<schema> ... </schema>>'

{ }

Map collection. Curly braces enclose maps ({ <key_datatype>:<value_datatype> }) or key value pairs ({ <key>:<value> }). A colon separates the key and the value.

;

Ends a CQL statement.

--

Separate command line options from command arguments with two hyphens. This syntax is useful when arguments might be mistaken for command line options.

Definition

If an option has a short and long form, both forms are given, separated by a comma.

Connection options

--all: List all connections.

-h, --host hostname: Node hostname or ip address.

-p, --port port: Remote jmx agent port number.

-pw, --password password: Remote jmx agent password.

-pwf, --password-file passwordFilePath: Remote jmx agent password file path.

-u, --username username: Remote jmx agent username.

Examples

To return all client statistics

nodetool clientstats --all

Address              Cipher Protocol  SSL       Version User      Keyspace  Requests Driver-Name                     Driver-Version
/10.101.33.110:56948 false  undefined undefined 66      cassandra OpsCenter 26551719 {product-brief} Java Driver 1.10.0-dse+20200217
/10.101.34.28:60254  false  undefined undefined 66      cassandra OpsCenter 32504215 {product-brief} Java Driver 1.10.0-dse+20200217
/10.101.32.233:46966 false  undefined undefined 66      cassandra           44049    {product-brief} Java Driver 1.10.0-dse+20200217
/10.101.32.233:47494 false  undefined undefined 66      cassandra           154225   {product-brief} Java Driver 1.10.0-dse+20200217
/10.101.33.110:56954 false  undefined undefined 66      cassandra           44064    {product-brief} Java Driver 1.10.0-dse+20200217
/10.101.32.233:47486 false  undefined undefined 66      cassandra           44042    {product-brief} Java Driver 1.10.0-dse+20200217
/10.101.33.110:56956 false  undefined undefined 66      cassandra system    44601    {product-brief} Java Driver 1.10.0-dse+20200217
/10.101.32.233:46830 false  undefined undefined 66      cassandra           44019    {product-brief} Java Driver 1.10.0-dse+20200217
/10.101.32.243:55374 false  undefined undefined 66      cassandra OpsCenter 48268    {product-brief} Java Driver 1.10.0-dse+20200217
/10.101.33.110:56946 false  undefined undefined 66      cassandra           44062    {product-brief} Java Driver 1.10.0-dse+20200217

Total connected clients: 10

User      Connections
cassandra 10