From 7dca40c55ead96d1841645402e2dc7b6bb6fdffc Mon Sep 17 00:00:00 2001 From: Artyom Date: Thu, 29 Oct 2026 03:52:27 +0300 Subject: [PATCH] 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) Claude-Session: https://claude.ai/code/session_01V1d3RLHNBBMA6UqBLLJv27 --- compose.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/compose.yaml b/compose.yaml index f84cb266..8beab4b6 100644 --- a/compose.yaml +++ b/compose.yaml @@ -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"