Re: Persisting stick tables on reload on 1.8

[Christian Greger]

Hi,

Thanks, it's working now. I saw peers mentioned elsewhere, but disregarded
that section since i was testing on a single instance.

On Thu, Apr 26, 2018 at 11:22 AM, Lukas Tribus  wrote:

> Hello Christian,
>
>
> On 26 April 2018 at 09:45, Christian Greger  wrote:
>
>> Hi,
>>
>> I was hoping the seamless reload in 1.8 would retain stick tables, but
>> I'm having no luck. Is it possible?
>>
>
>
> Stick tables can be transferred from the old to the new process while
> reloading by configuring the peers section with a local hostname, this is
> supported since haproxy 1.5:
>
> http://cbonte.github.io/haproxy-dconv/1.5/configuration.html#3.5-peer
>
>
>
> 1.8's seamless reload feature is about the actual listening sockets only.
>
>
>
> cheers,
> lukas
>
>


-- 

Christian Greger
977 65 075/ luxi2...@gmail.com

[image: Twitter]  [image: Google Plus]
 [image: Skype]

This e-mail message may contain confidential or legally privileged
information and is intended only for the use of the intended recipient(s).
Any unauthorized disclosure, dissemination, distribution, copying or the
taking of any action in reliance on the information herein is prohibited.
E-mails are not secure and cannot be guaranteed to be error free as they
can be intercepted, amended, or contain viruses. Anyone who communicates
with us by e-mail is deemed to have accepted these risks. Company Name is
not responsible for errors or omissions in this message and denies any
responsibility for any damage arising from the use of e-mail. Any opinion
and other statement contained in this message and any attachment are solely
those of the author and do not necessarily represent those of the company.

Re: Persisting stick tables on reload on 1.8

[Lukas Tribus]

Hello Christian,


On 26 April 2018 at 09:45, Christian Greger  wrote:

> Hi,
>
> I was hoping the seamless reload in 1.8 would retain stick tables, but I'm
> having no luck. Is it possible?
>


Stick tables can be transferred from the old to the new process while
reloading by configuring the peers section with a local hostname, this is
supported since haproxy 1.5:

http://cbonte.github.io/haproxy-dconv/1.5/configuration.html#3.5-peer



1.8's seamless reload feature is about the actual listening sockets only.



cheers,
lukas