nodetool gossipinfo

Returns the gossip information to discover broadcast protocol between nodes in a cluster.

Synopsis

nodetool [<connection_options>] gossipinfo

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.

-h, --host hostname: The hostname or IP address of a remote node or nodes. When omitted, the default is the local machine.
-p, --port jmx_port: The JMX port number.
-pw, --password jmxpassword: The JMX password for authenticating with secure JMX. If a password is not provided, you are prompted to enter one.
-pwf, --password-file jmx_password_filepath: The filepath to the file that stores JMX authentication credentials.
-u, --username jmx_username: The username for authenticating with secure JMX.

Examples

Show gossip information for cluster

nodetool gossipinfo

127.0.0.1
  generation:1532896921
  heartbeat:2038494
  STATUS:1611484:NORMAL,8242717283351148695
  LOAD:2038483:262546.0
  SCHEMA:975284:d4f18346-f81f-3786-aed4-40e03558b299
  DC:26:Search
  RACK:18:rack1
  RELEASE_VERSION:4:4.0.0.602
  NATIVE_TRANSPORT_ADDRESS:3:127.0.0.1
  X_11_PADDING:11503:{"dse-version":"6.9.x","workloads":"SearchGraphCassandraAnalytics","workload":"SearchAnalytics","active":"true","server_id":"FA-16-3E-17-A6-6F","graph":true,"health":0.9}
  NET_VERSION:1:256
  HOST_ID:2:3b8e8192-c1d3-4b01-a792-9673b4e377c1
  NATIVE_TRANSPORT_READY:121:true
  NATIVE_TRANSPORT_PORT:6:9042
  NATIVE_TRANSPORT_PORT_SSL:7:9042
  STORAGE_PORT:8:7000
  STORAGE_PORT_SSL:9:7001
  JMX_PORT:10:7199
  TOKENS:1611483:&lt;hidden>
/127.0.0.2
  generation:1576523508
  heartbeat:1010423
  STATUS:1010421:shutdown,true
  LOAD:1010437:3.13473671E8
  SCHEMA:714345:bbf9280d-4cb4-357f-9e2c-bf88ec70db22
  DC:14:Cassandra
  RACK:17:rack1
  RELEASE_VERSION:4:4.0.0.676
  NATIVE_TRANSPORT_ADDRESS:3:127.0.0.2
  DSE_GOSSIP_STATE:1010409:{"dse-version":"6.9.0","workloads":"Cassandra","workload":"Cassandra","active":"false","server_id":"FA-16-3E-8C-6D-1A","graph":false,"health":1.0,"blacklisted":"true"}
  NET_VERSION:1:512
  HOST_ID:2:a9013cb4-ae3f-4c85-a8b9-a5d94b587fe0
  NATIVE_TRANSPORT_READY:1010419:false
  NATIVE_TRANSPORT_PORT:7:9042
  NATIVE_TRANSPORT_PORT_SSL:8:9042
  STORAGE_PORT:9:7000
  STORAGE_PORT_SSL:10:7001
  JMX_PORT:11:7199
  SCHEMA_COMPATIBILITY_VERSION:5:1
  TOKENS:1001732:&lt;hidden>

nodetool gossipinfo

Synopsis

Options

Examples

Show gossip information for cluster

Was this helpful?

Give Feedback