You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "Nodes Status" panel from the "Cassandra Overview" dashboard uses the following query to determine if a node is considered up:
max by (cluster, dc, rack, instance) (changes(mcac_thread_pools_completed_tasks{cluster=~"$cluster", dc=~"$dc", rack=~"$rack", instance=~"$node", pool_name="gossip_stage"}[2m:30s])) > bool 0
For single node clusters the GossipStage ThreadPool is always 0.
I know this is an edge case but having for example single-node test instances displayed as DOWN is annoying. Isn't there a better metric? nodetool status is showing single-node clusters as up, does someone know what metric they are using?
The text was updated successfully, but these errors were encountered:
The "Nodes Status" panel from the "Cassandra Overview" dashboard uses the following query to determine if a node is considered up:
For single node clusters the GossipStage ThreadPool is always 0.
I know this is an edge case but having for example single-node test instances displayed as DOWN is annoying. Isn't there a better metric?
nodetool status
is showing single-node clusters as up, does someone know what metric they are using?The text was updated successfully, but these errors were encountered: