Alerts: AnkusaDiskLow
The file system holding data_dir has less than 10 % free. At zero the store cannot commit: every hook is 503 store_unavailable (nothing is acked), /ready answers 503 and the load balancer drains the node. Acked hooks are safe; RocksDB writes nothing it cannot sync.
ankusa_disk_free_bytes / ankusa_disk_total_bytes: the alert's ratio. Reported only while :disksup runs, which the server image starts; an embedder without :os_mon has no disk series and no alert.ankusa_store_disk_bytes: the store's own size, against what else is on the volume.ankusa_queue_pending and ankusa_queue_scheduled (a backlog), ankusa_dlq_rows/ankusa_dlq_bytes, ankusa_queue_archive_pending and ankusa_archive_oldest_unarchived_age_seconds (hooks waiting for an archive segment), ankusa_quarantine_bytes, ankusa_audit_bytes.ankusa_store_write_failures_total{class="no_space"} once it is full.ankusa_compact_failures_total{stage="segment"}, see dlq-growth and storage. DLQ: dlq-growth. Quarantine: DELETE /v1/quarantine (scope quarantine:write) after replaying what matters.data_dir by hand: RocksDB's files are not independent, and segments/ under LocalFS is the archive.node.min_free_bytes so /ready flips at the floor, before the store hits ENOSPC: the node leaves the load balancer with its data intact (deployment).503 and resume once space frees; the store closes and reopens (at most every 5 s, then backing off to 60 s) to clear a latched write error (storage). No restart is needed.ankusa_disk_free_bytes / ankusa_disk_total_bytes is above 0.10 and not falling.GET /ready answers 200 with "store": "ok" and, with node.min_free_bytes set, "disk": "ok".ankusa_store_write_failures_total{class="no_space"} stops rising; ankusa_store_unavailable_seconds is 0.201.Can you improve this documentation?Edit on GitHub
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |