troubleshoot-cockroachdb

Troubleshoot CockroachDB raft liveness failures by mapping Netdata health signals to dominant failure archetypes. Use the operator playbook diagnostic tree and CockroachDB-specific MCP queries to identify liveness loss, then verify remediation by re-running queries for clean anomaly results.

Diagnose LSM compaction death spirals in CockroachDB by querying Netdata collector contexts via MCP. Apply the operator playbook logic to match observed health signals against the compaction death spiral archetype, distinguishing it from clock skew, hot ranges, or intent accumulation.

Validate CockroachDB remediation by re-running the same Netdata MCP queries used during triage. Check the specified load-bearing contexts to ensure a clean anomaly result, confirming the hot range bottleneck or intent accumulation issue is fully resolved.

Use Netdata to triage CockroachDB clock skew crises and unexpected restarts by routing health signals through the diagnostic tree. Query CockroachDB-specific MCP contexts to match symptoms against the clock skew crisis archetype for structured incident resolution.

Diagnose CockroachDB intent accumulation by querying specific Netdata CockroachDB collector contexts via MCP. Follow the diagnostic tree to verify whether observed latency and saturation signals match the intent accumulation archetype before recommending remediation steps.

This triage approach covers specific CockroachDB failure archetypes: LSM compaction death spirals, raft liveness failures, clock skew crises, hot ranges, and intent accumulation. It routes Netdata signals through the operator playbook to match the correct archetype during incident remediation.