Give the balancer time to see the replicas before it counts as unhealthy

The balancer reports itself unhealthy while no replica is up, and its
start period of 10 s was shorter than the time the replicas need on a
busy host: they wait for migrate and s3-init and have a 30 s start
period of their own. docker compose up --wait then failed on a cold
start although the stand came up seconds later. A 60 s start period
with 1 s probes keeps the balancer starting, not unhealthy, until the
first replica is in rotation.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V1d3RLHNBBMA6UqBLLJv27
This commit is contained in:
Artyom
2026-10-29 03:52:27 +03:00
co-authored by Claude Opus 5.5
parent de9dc61ebc
commit 7dca40c55e
+2 -1
View File
@@ -51,7 +51,8 @@ services:
interval: 2s
timeout: 2s
retries: 3
start_period: 10s
start_period: 60s
start_interval: 1s
sysctls:
net.ipv4.ip_local_port_range: "10240 65535"
net.ipv4.tcp_tw_reuse: "1"