fix(metrics): stop vmbackup being OOMKilled at 256Mi #23

Merged

sean merged 1 commit from fix/vmbackup-oom into trunk 2026-08-10 11:47:07 +00:00

Conversation 0 Commits 1 Files changed 1 +8 -2

sean commented 2026-08-10 11:45:54 +00:00

Owner

Copy link

Follow-up to #22, caught during verification. The sidecar landed with limits.memory: 256Mi and was OOMKilled 5 times before a run completed - each restart redoing the whole upload.

vmbackup buffers whole parts, and this data set has single parts near 500 MB (data/indexdb/2026_08/*/items.bin). The first backup is also the worst case - a full 11.87 GiB upload - because later runs are incremental against the same -dst.

Raises limit to 1Gi, request to 128Mi. The backup did finally report backup OK, so this is a stability fix rather than a correctness one.

Follow-up to #22, caught during verification. The sidecar landed with `limits.memory: 256Mi` and was **OOMKilled 5 times** before a run completed - each restart redoing the whole upload. vmbackup buffers whole parts, and this data set has single parts near **500 MB** (`data/indexdb/2026_08/*/items.bin`). The first backup is also the worst case - a full **11.87 GiB** upload - because later runs are incremental against the same `-dst`. Raises limit to 1Gi, request to 128Mi. The backup did finally report `backup OK`, so this is a stability fix rather than a correctness one.

sean added 1 commit 2026-08-10 11:45:55 +00:00

fix(metrics): stop vmbackup being OOMKilled at 256Mi ... db3ebe1617

The sidecar landed with limits.memory 256Mi. That was too low. It was
OOMKilled 5 times before a run completed, and each restart redid the
whole upload from the start.

vmbackup buffers whole parts, and this data set has single parts near
500 MB (data/indexdb/2026_08/*/items.bin). The first backup is also the
worst case, a full 11.87 GiB upload, because later runs are incremental
against the same -dst.

Raises the limit to 1Gi and the request to 128Mi. The backup did finally
report 'backup OK', so this is a stability fix, not a correctness one.

sean merged commit db3ebe1617 into trunk 2026-08-10 11:47:07 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

sean/olly!23

No description provided.