Postgres archive_command has no timeout; a hung wal-push stops WAL archiving

Aperta
  • Qualcosa non va?
#226 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
bash, go, postgresql
Ambito
cli, database

Direzione di ricerca

Find the onebox-wal-g wrapper in the repo's backup directory and wrap the wal-push call with timeout. Then read the Go sources for ob backup status and ob doctor to add reporting of last_archived_time age and .ready backlog. Done when stalled uploads fail fast and the CLI shows archive lag.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

The Postgres archive_command Onebox installs (/opt/onebox/backup/onebox-wal-g wal-push %p) has no time limit. When one upload stalls, archiving stops for good: Postgres waits on that command and retries the same segment, and WAL accumulates in pg_wal until the disk fills. The off-site recovery point falls behind for the whole stall, so the backup's 5-minute target is silently missed.

What happened

Goal production, 2026-10-24. A catalog refresh wrote WAL faster than the archiver uploaded it to Hetzner object storage (hel1), and pg_wal grew to 37 GB with about 2,250 segments marked .ready. While that backlog drained, wal-g wal-push hung twice:

  • at 23:07 UTC on 000000020000005B000000DF, for 7 minutes;
  • at 23:47 UTC on 000000020000006200000067, for more than 6 minutes;
  • in each case pg_stat_archiver.last_archived_time stopped advancing while failed_count stayed 0, and the wal-g process produced no further log output;
  • killing the wal-g process let the archiver retry the segment, and uploads resumed straight away.

Postgres shares the host disk with the application, so an unnoticed hang ends with the database unable to write. Because failed_count stays 0, a check on archive failures does not catch it.

Proposal

  • Bound each wal-push in the wrapper, for example with timeout or wal-g's own upload timeout, so a stalled upload fails and Postgres retries it.
  • Have ob backup status and ob doctor report archive lag: the age of last_archived_time and the .ready backlog, not only failures.

Related

ob plan also refuses a live release whose onebox.snapshot.yml is still onebox.run/v1alpha1 ("snapshot unusable: schema_identity_unsupported"). That blocks the first deploy after a project moves to v1alpha2. Goal worked around it by editing the snapshot's apiVersion line on the host. The 2026-10-04 decision record says the two schemas differ only by identity when there is no execution block, so loading such a snapshot as v1alpha2 would remove the need for that edit.

Lingua principale
Go
Stelle
4
Fork
0
Merge medio
36m
PR unite (30g)
13

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di labstack/onebox

Tutte le issue di labstack/onebox

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.