investigate reload timeout issue

docker-archive / dockercloud-haproxy

HAproxy image that autoreconfigures itself when used in Docker Cloud

https://cloud.docker.com/

651 stars 187 forks source link

Closed tifayuki closed 7 years ago

tifayuki commented 7 years ago

Is if the issue described in https://github.com/docker/dockercloud-haproxy/issues/172 happens to only one version of haproxy or to any version.

May change the default value of RELOAD_TIME=0 to -1 if it is a real problem to all version of haproxy.

tifayuki commented 7 years ago

It turned out that the old process doesn't get reaped because of the configuration file is invalid

When this happen, the haproxy failed to start and leaving the old process running forever. Fixed in version 1.6.7