(ozone) branch master updated: HDDS-17154. S3 Gateway HAProxy in compose environments exits at startup if s3g1..s3g3 are not resolvable yet (#11634)

[si...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

smengcl pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ozone.git


The following commit(s) were added to refs/heads/master by this push:
     new 1753288f333 HDDS-17154. S3 Gateway HAProxy in compose environments exits at startup if s3g1..s3g3 are not resolvable yet (#11634)
1753288f333 is described below

commit 1753288f3336cd4220ac90c161452e98b1e66b91
Author: Siyao Meng <50...@users.noreply.github.com>
AuthorDate: Tue Oct 20 16:26:50 2026 -0700

    HDDS-17154. S3 Gateway HAProxy in compose environments exits at startup if s3g1..s3g3 are not resolvable yet (#11634)
    
    Co-authored-by: Claude Opus 5.5 <no...@anthropic.com>
---
 hadoop-ozone/dist/src/main/compose/common/s3-haproxy.cfg | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/hadoop-ozone/dist/src/main/compose/common/s3-haproxy.cfg b/hadoop-ozone/dist/src/main/compose/common/s3-haproxy.cfg
index 18d71a23469..72784ae5bbf 100644
--- a/hadoop-ozone/dist/src/main/compose/common/s3-haproxy.cfg
+++ b/hadoop-ozone/dist/src/main/compose/common/s3-haproxy.cfg
@@ -21,8 +21,15 @@ global
     daemon
     maxconn 256
 
+# Resolve the S3 Gateways through Docker's embedded DNS at runtime, so HAProxy starts
+# (and keeps retrying) even if s3g1..s3g3 are not resolvable yet when it starts.
+resolvers docker
+    nameserver dns 127.0.0.11:53
+    hold valid 10s
+
 defaults
     mode http
+    default-server init-addr last,libc,none resolvers docker
     timeout connect 5000ms
     timeout client 50000ms
     timeout server 50000ms


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@ozone.apache.org
For additional commands, e-mail: commits-help@ozone.apache.org