Using CHouse UIMonitoring

Cluster

Mutations, replication queue, blocked-task indicators and per-replica lag from system.mutations and system.replicas.

In the app
Monitoring › Cluster/monitoring/cluster
Monitoring › Cluster in CHouse UI
Monitoring › Cluster

Monitoring › Cluster (/monitoring/cluster, permission cluster:view) answers is the machinery stuck? — mutations, replication, topology, the insert backlog and ON CLUSTER DDL at a glance.

Panels

Mutations (system.mutations)

  • Every mutation with status chips (done / pending / failed)
  • Sortable by age — stuck mutations bubble to the top

Replication queue (system.replication_queue)

  • Pending replication tasks per table
  • Long-lived queue entries indicate a replica falling behind or a ZooKeeper/Keeper issue

Per-replica status (system.replicas)

  • Lag per replica (absolute and relative to the leader)
  • Queue depth per replica

Topology (system.clusters)

Shards and replicas of each cluster, with per-host health such as error counts — check it when lag or DDL points at one host.

Insert backlog (system.distribution_queue)

Inserts into Distributed tables waiting to be sent to their shards. A growing backlog means a shard is unreachable or slow. (Shown as unavailable on servers without this table.)

DDL queue (system.distributed_ddl_queue)

ON CLUSTER DDL from the last day per host, so a statement stuck or failed on one replica is visible.

DDL simulator

Paste an ALTER TABLE … UPDATE or ALTER TABLE … DELETE to estimate it before running it: affected rows, parts and bytes rewritten, duration and disk needed. It only runs read-only estimate queries — it never executes the mutation — and accepts nothing but UPDATE/DELETE mutations.

Blocked-task indicator strip

A compact strip aggregates the four "cluster is struggling" signals:

SignalThreshold behavior
Long queriesQueries running past a threshold
Long mergesMerges taking too long
Open mutationsMutations pending too long
Max replica lagThe worst replica lag in the cluster

A non-empty strip means: look at parts and the tables below before trusting dashboards.

Typical reads

Strip stateMeaningFirst check
EmptyMachinery healthyNothing
Long merges + many partsIngest rate outpacing mergesParts view, schema advisor
Open mutationsSomeone ran heavy ALTERsMutations table
Max replica lagA replica is behindPer-replica panel; Keeper health in Metrics → ZooKeeper

Underlying data

TableUsed for
system.mutationsMutations panel
system.replication_queueQueue panel
system.replicasReplica lag/depth
system.clustersTopology
system.distribution_queueInsert backlog
system.distributed_ddl_queueDDL queue
system.query_logLong-query signal in the strip

Tip: Pair this tab with a threshold alert on replica lag — the strip tells you when you're on the page; the alert tells you when to open the page.

Edit this page on GitHub ↗