# HAProxy 1.7 server hot reconfiguration added?

**URL:** <https://discourse.haproxy.org/t/haproxy-1-7-server-hot-reconfiguration-added/1528>\
**Category:** Help!\
**Created:** [August 22, 2017, 8:36pm UTC](https://discourse.haproxy.org/t/haproxy-1-7-server-hot-reconfiguration-added/1528 "2017-08-22T20:36:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ADV-IT](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/adv-it/32/265_2.png) [@ADV-IT](https://discourse.haproxy.org/u/ADV-IT)\
**Post date:** [August 22, 2017, 8:36pm UTC](https://discourse.haproxy.org/t/haproxy-1-7-server-hot-reconfiguration-added/1528/1 "2017-08-22T20:36:41Z")

</div>

Hi All,  
On web site [www.haproxy.org](http://www.haproxy.org) I see this

- version 1.7 : added server hot reconfiguration, content processing agents, multi-type certs,

B​ut cannot find any info about something NEW regarding Hot Server Reconfiguration process.  
In documentation, only old process of reload (/etc/init.d/haproxy reload​) mentioned.​

​What exactly added into v1.7​ for server hot reconfiguration?

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [August 24, 2017, 9:09am UTC](https://discourse.haproxy.org/t/haproxy-1-7-server-hot-reconfiguration-added/1528/2 "2017-08-24T09:09:35Z")

</div>

Double post from the mailing list:  
[https://www.mail-archive.com/haproxy@formilux.org/msg27123.html](https://www.mail-archive.com/haproxy@formilux.org/msg27123.html)

From the 1.7 announcement:  
[https://www.mail-archive.com/haproxy@formilux.org/msg24244.html](https://www.mail-archive.com/haproxy@formilux.org/msg24244.html)

I believe its about those 2 new features:

> - init-addr : it is now possible to decide in which order the FQDN should be resolved on “server” lines, and even accept to start with no address, waiting for a run-time resolution.
> - server update on the CLI : the CLI makes it possible to change a server’s address, port, maxconn, check address and port so that it is not required anymore to reload haproxy just to update an address. **In conjunction with init-addr, it even allows to pre-populate some server pools that are filled at run time**.