Cluster Status

The database administrator may execute the faunadb-admin status command against any node in the cluster. The command returns the cluster’s status from the point of view of the node executing the command. In normal operations, all nodes should have the same point of view.

Replica: asia-east (data+log)
Status  State  WorkerID  Log Segment  Address     Owns   Goal   HostID
up      live   516       Segment-2   31.2%  31.2%  d3f4039a-19e7-44f9-9ff0-fbb84873301c
up      live   519       Segment-0  37.3%  37.3%  751ab602-515f-4410-b541-5a022b7f20fb
up      live   520       Segment-1  27.0%  31.5%  bee6efeb-a159-445c-9073-7442a42d6906

Replica: us-west (data+log)
Status  State  WorkerID Log Segment  Address          Owns   Goal   HostID
up      live   512      Segment-0    12.567.130.208   30.7%  30.7%  1a99f8f1-102f-49c7-8493-55d53d7fe006
up      live   513      Segment-2    12.567.92.245    48.9%  38.9%  2a91b55d-e5f6-4a56-9103-0371152de804
up      live   514      Segment-1    12.567.197.208   20.4%  30.4%  d3b47f57-e64b-4f07-9e69-f2995e65f9e1

Cluster field descriptions

Heading Description


If the node is seen as alive, then the status will be "up" or else it will be reported as "down".


If the node is operational, it is "live". If the node has been removed from the cluster, but it can still participate in data transfers if it is not shut down, then the state will be "removed".


The unique id given by fauna cluster membership.

Log Segment

If this node is a log node, then the log segment will be displayed.


The network address used by the nodes to communicate with each other.


The current percentage of data owned by this node for its replica.


The target percentage of data that should be owned for its replica.


The unique address for this host.

Data movement

Each replica will print out all of its nodes in a group. When a replica owns less than 100% of the data, then data must be transferred from other replicas in the cluster to fill in the missing data. When an individual node in a replica has an Owns value that equals its Goal value, then no data movement is required for this node. When Owns is greater than Goal, then data will be removed or transferred off this node. When Owns is less than Goal, then data must be transferred to this node. See Replica: us-west above for nodes which require data movement.

Was this article helpful?

We're sorry to hear that.
Tell us how we can improve!

Thank you for your feedback!