liveBook · Manning

Node status

As explained in ScyllaDB in Action

Node status indicates whether a database node is up and healthy or down and unavailable.

Node status shows whether a ScyllaDB node is up and taking traffic or down because it is unhealthy and unavailable. The nodetool status command lists each node’s status alongside its state, data ownership, address, and cluster location. section 2.1.2

Read the status letter in nodetool output as follows:

Checking a node

Run nodetool status --resolve-ip to inspect the cluster with friendlier node names. In output such as UN scylla-1, the first character, U, confirms that scylla-1 is up; the second character, N, describes its separate normal state. section 2.1.2

Table 2.1 Possible values for the node’s status
Status letter
Meaning
Description
U
Up
Node is taking traffic
D
Down
Node is unhealthy and not taking traffic

Use the status table to distinguish an available node from an unhealthy node that has stopped taking traffic. section 2.1.2

How ScyllaDB in Action covers it

How deep it goes
Defines Up and Down operational meanings and distinguishes status from the separate node-state indicator.
Examples
Uses nodetool status --resolve-ip and the output code UN to demonstrate an up, normally operating node.
What it assumes
Assumes access to a running ScyllaDB container and basic Docker shell usage.
What you can do after
Operate/configure a cluster by checking node availability with nodetool status.
How it connects
Connects node status with ScyllaDB clusters, nodetool, node state, datacenters, and racks.

This explainer was generated by Manning's knowledge graph from the text of ScyllaDB in Action. The section links point to the parts of the book it draws on.