Hi, Could you please tell us about the motivation behind introducing SRV_ADMF_CMAINT flag? We were planning to avoid haproxy reloads by adding "dummy" servers in the configuration in "disabled" mode and then "set server addr" and "enable" socket commands to enable them on-demand. And that, we now won't be able to do with the introduction of SRV_ADMF_CMAINT flag.
We want to avoid reloads because we have persistent TCP connections being served via haproxy and with a reload the previous haproxy process keeps on serving the old connections and we lose stats for those connections as the new process is not aware of them for obvious reasons. Avoiding reload also avoids stats counters being reset. - Pradeep Jindal On Tue, Sep 15, 2015 at 12:15 PM, Cyril Bonté <[email protected]> wrote: > Hi, > > > Le 14/09/2015 14:23, Ayush Goyal a écrit : > >> Hi, >> >> We are testing haproxy-1.6dev4, we have added a server in backend as >> disabled, but we are not able >> to bring it up using socket command. >> >> Our backend conf looks like this: >> >> =====cut==== >> backend apiservers >> server api101 localhost:1234 maxconn 128 weight 1 check >> server api102 localhost:1235 disabled maxconn 128 weight 1 check >> server api103 localhost:1236 disabled maxconn 128 weight 1 check >> =====cut==== >> >> But, when I run the "enable apiservers/api103" command, it is still in >> MAINT mode. Disabling and enabling of non "disabled" servers like api101 >> are happening properly. >> >> Enabling a config "disabled" server works correctly with haproxy1.5. Can >> you confirm whether its a bug in 1.6-dev4? >> > > This is due to the introduction of the SRV_ADMF_CMAINT flag, which is set > permanently. The "enable/disable" socket command will only modify the > SRV_ADMF_FMAINT and SRV_ADMF_FDRAIN flags. > > I add Baptiste to the thread. > > -- > Cyril Bonté > >
