crdb_replication_unavailable_ranges

Number of ranges with fewer live replicas than needed for quorum

Dimensions:None

Technical Annotations (15)

Configuration Parameters (3)

constraints

Replica placement constraints that may conflict with voter_constraints or lease_preferences

voter_constraints

Constraints for voting replicas that must align with general constraints

lease_preferences

Lease holder preferences that must be consistent with constraint topology

CLI Commands (2)

SHOW ZONE CONFIGURATION FOR TABLE movr.users;diagnostic

ALTER TABLE movr.users CONFIGURE ZONE DISCARD;remediation

Technical References (10)

rangesconceptreplicasconceptmulti-cloud deploymentconceptRaft-based replicationprotocolUS-East-1componentcritical nodes endpointcomponentranges_unavailablecomponentquorumconceptzone configurationsconceptranges.unavailablecomponent

Related Insights (10)

Cluster Unavailability Despite DB Console Accessibilitycritical

When cluster loses quorum, ranges become unavailable and queries fail, yet DB Console and Prometheus endpoint may remain accessible (served from unavailable node's cache). Operators can be misled by accessible monitoring showing stale data while cluster is actually down, delaying incident response.

▸

CockroachDB unavailable ranges cause data inaccessibilitycritical

▸

Single cloud provider outage causes multi-service application downtimecritical

▸

Constraint violations from logically inconsistent zone configurationcritical

▸

Unavailable ranges cause data loss risk and immediate outagecritical

▸

Unavailable ranges indicate quorum losswarning

▸

Non-zero unavailable ranges indicate cluster instabilitycritical

▸

Replicas not conforming to zone configurations or placement policieswarning

▸

Ranges unavailable due to insufficient quorumcritical

▸

Node count drop indicates dead or unresponsive nodescritical

▸