Re: Observations about reloads and DNS SRV records

2018-08-21 Thread francis Lavalliere
This is related to the discourse thread (And also discuss the issues in ML instead of discourse). https://discourse.haproxy.org/t/config-reload-with-dynamic-service-discovery-via-dns/2625/10 Here are the findings from my ends: 1 - State file / Port range invalid conversion In the haproxy

Re: Observations about reloads and DNS SRV records

2018-07-04 Thread Tait Clarridge
Hey Baptiste, I’ll try it out next week when I get back (currently on vacation) and let you know. Thanks! Tait On Tue., Jul. 3, 2018 at 06:24 Baptiste wrote: > Hi, > > Actually, the problem was deeper than my first thought. > In its current state, statefile and SRV records are simply not

Re: Observations about reloads and DNS SRV records

2018-07-03 Thread Baptiste
Hi, Actually, the problem was deeper than my first thought. In its current state, statefile and SRV records are simply not compatible. I had to add a new field in the state file format to add support to this. Could you please confirm the patch attached fixes your issues? Baptiste On Mon, Jun

Re: Observations about reloads and DNS SRV records

2018-06-25 Thread Baptiste
Hi, Forget the backend id, it's the wrong answer to that problem. I was investigating an other potential issue, but this does not fix the original problem reported here. Here is the answer I delivered today on discourse, where other people have also reported the same issue: Just to let you

Re: Observations about reloads and DNS SRV records

2018-06-22 Thread Baptiste
Hi Tait, There is a first thing you can do to prevent this from happening, but this might be complicated to implement. If you force a backend id in the configuration file, the problem won't exist anymore... backend be server-template srv 5 _http._tcp.srv.tld resolvers dnsserver

Re: Observations about reloads and DNS SRV records

2018-06-10 Thread Tait Clarridge
On Sun, Jun 10, 2018 at 3:22 AM Baptiste wrote: > > Thanks for giving me this idea! > I wrote a quick and inflexible one here: > https://github.com/bedis/dnsserver > So feel free to contribute to it or write your own :) > > I'm going to use it to troubleshoot the issue you reported. That said, >

Re: Observations about reloads and DNS SRV records

2018-06-10 Thread Tait Clarridge
Hey Baptiste, On Sun, Jun 10, 2018 at 3:19 AM Baptiste wrote: > > ==> while writing this mail, I am able to reproduce the issue I think: > - start HAProxy with SRV records > - dump servers state > - update haproxy conf to prevent dns resolution at runtime > - reload haproxy > ==> my servers are

Re: Observations about reloads and DNS SRV records

2018-06-10 Thread Baptiste
> > I'm a little swamped with other work at the moment, but when I get a > chance I would be able to provide a DNS server (written in Go) that returns > additional records to test with if that helps. > Thanks for giving me this idea! I wrote a quick and inflexible one here:

Re: Observations about reloads and DNS SRV records

2018-06-10 Thread Baptiste
Hi Tait, 1. Reloading with SRV records ignores server-state-file > Can you tell me more about this one. How do you see that? I mean, I have a conf similar to yours and I can see HAProxy parsing the server state file (and returning a bunch of warning I'm working on about backend name and ID

Re: Observations about reloads and DNS SRV records

2018-06-07 Thread Tait Clarridge
Hi Baptiste, thanks for the response. On Wed, Jun 6, 2018 at 6:32 PM Baptiste wrote: > > This should not happen and it's a known issue that we're working on. > > Excellent, figured you guys were probably already aware of it. Let me know if I can assist in testing. > > Actually, I tested many

Re: Observations about reloads and DNS SRV records

2018-06-06 Thread Baptiste
Hi Tait A few comments inline: 1. Reloading with SRV records ignores server-state-file > - While this is not a huge deal, it does mean that the backend in > question becomes unavailable when the proxy is reloaded until the SRV and > subsequent A records are resolved > - I understand that

Re: Observations about reloads and DNS SRV records

2018-06-06 Thread Tait Clarridge
On Wed, Jun 6, 2018 at 11:35 AM Aleksandar Lazic wrote: > Hi Tait. > > On 06/06/2018 11:16, Tait Clarridge wrote: > >I've been testing DNS service discovery and the use of SRV records and > have > >a few thoughts on a couple things that I noticed. > > In this area was a lot of changes in the

Re: Observations about reloads and DNS SRV records

2018-06-06 Thread Aleksandar Lazic
Hi Tait. On 06/06/2018 11:16, Tait Clarridge wrote: I've been testing DNS service discovery and the use of SRV records and have a few thoughts on a couple things that I noticed. In this area was a lot of changes in the last version of haproxy, do you have tested the setup with the latest

Observations about reloads and DNS SRV records

2018-06-06 Thread Tait Clarridge
I've been testing DNS service discovery and the use of SRV records and have a few thoughts on a couple things that I noticed. 1. Reloading with SRV records ignores server-state-file - While this is not a huge deal, it does mean that the backend in question becomes unavailable when the proxy