Starting with HAProxy 1.8, which is scheduled to arrive late in 2017, it's possible to reload HAProxy without dropping packets in the process.
This might also be of interest in the scope of #195, because I assume that open/stalled connections may be blocking the restart.
In addition to seamless reloads we should implement this new feature:
- hard-stop-after: this new global setting forces old
processes to quit after a delay consecutive to a soft reload operation.
This is mostly used to avoid an accumulation of old processes in some
environments where idle connections are kept with large timeouts.
Starting with HAProxy 1.8, which is scheduled to arrive late in 2017, it's possible to reload HAProxy without dropping packets in the process.
This might also be of interest in the scope of #195, because I assume that open/stalled connections may be blocking the restart.
In addition to seamless reloads we should implement this new feature: