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.

Options

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

--all: List all connections.

--host <hostname_or_IP>: The hostname or IP address of the DSE node to connect to. If included, the command won’t connect to the local node.

If omitted, the default is the local node.

Also accepts the short form -h.

-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

Result

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

Total connected clients: 10

User      Connections
cassandra 10

nodetool clientstats

Synopsis

Options

Examples

Was this helpful?

Give Feedback