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

Aberta
  • Algo errado?
#226 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
55/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
bash, go, postgresql
Domínio
cli, database

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Go
Estrelas
4
Forks
0
Merge médio
36min
PRs com merge (30d)
13

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de labstack/onebox

Todas as issues de labstack/onebox

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.