# Leastconn connections count after reload

**URL:** <https://discourse.haproxy.org/t/leastconn-connections-count-after-reload/7609>\
**Category:** Help!\
**Created:** [April 28, 2022, 1:44am UTC](https://discourse.haproxy.org/t/leastconn-connections-count-after-reload/7609 "2022-04-28T01:44:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![felipewd](https://avatars.discourse-cdn.com/v4/letter/f/0ea827/32.png) [@felipewd](https://discourse.haproxy.org/u/felipewd)\
**Post date:** [April 28, 2022, 1:44am UTC](https://discourse.haproxy.org/t/leastconn-connections-count-after-reload/7609/1 "2022-04-28T01:44:04Z")

</div>

Hi everyone!

This is most likely a newbie question, but I couldn’t find the answer anywhere: I use `leastconn` for long connections in TCP mode.

When I need to reload haproxy (after a conf update), does the new process inherit the connections count in order to preserve the correct behavior regarding the balance? This is crucial for our application. (we use the admin socket with `expose-fd listeners` for seamless reload with `-x` reload.

I’m using a master-worker (systemd) mode here, but not sure if this is relevant for this question.

Thanks!