Bound fresh restore database initialization by observed startup latency

This commit is contained in:
archipelago
2026-10-08 04:22:25 -04:00
parent f9661946ab
commit 1a409900d9
3 changed files with 51 additions and 3 deletions
+4 -1
View File
@@ -720,7 +720,10 @@ class Controller:
self.run(['podman','start',identifier])
# The image bootstrap server accepts Unix sockets before it exits;
# TCP readiness waits for the final server, avoiding interrupted restore.
deadline=time.monotonic()+90
# Exact recovery-image qualification under host I/O pressure reached
# final TCP readiness at 104 seconds. Give only this fresh initdb
# startup 180 seconds; probes remain bounded and restore is not retried.
deadline=time.monotonic()+180
while True:
remaining=deadline-time.monotonic()
require(remaining>0,'Backup restore database did not become ready')