Add docs on best practices for avoiding out-of-disk (OOD) scenarios

[rmloveland]

Richard Loveland (rmloveland) commented:

Via @mwang1026:

Our docs don't talk a lot about the OOD scenario -- why it's so nefarious (you need to write data to delete data, e.g.) and how to avoid it (read: alert alert alert, vertically scale if you have persistent disk like EBS, otherwise you have to horizontally scale before you run out of space / make space by removing ballast and log files but at that point you might not have enough space)

We have this doc, but we don't talk about the alerting you should set up about disk outage -- how a ballast might not be enough if you want to horizontally scale -- and generally best practices to avoid OOD situations. We could separate this into a separate issue.

aka: ballast file best practices, handling OOD scenarios

See also:

• storage: automatic ballast files #11156

Jira Issue: DOC-1219

[github-actions]

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
10 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB docs!