cockroachdb / cockroachdb/cockroach

storage: a node with a faulty (but not failed) disk causes a cluster availability outage

Open
#129,579 3 comments 0 reactions 0 assignees View on GitHub
A-kv-distribution A-storage branch-master C-bug O-postmortem O-support P-3 T-kv
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

**Describe the problem**

A node with a faulty disk may not be detected by the disk stall detector. If some IO requests stall or fail, but others succeed, the node can remain in a degraded state indefinitely. This can result in a cluster level availability outage. We don't have any testing simulating this situation or an approach to address it.

Either KV or storage layer should detect and handle this.

**To Reproduce**

This happened on a serverless cluster and caused transient unavailability for ~20 hour until the disk problem was finally detected by the disk stall detector. This impacted all the customers on the cluster during that window.

**Environment:**
- CockroachDB version v24.1.2
- Serverless cluster

Jira issue: CRDB-41602

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.