Re: make haproxy notice that backend server ip has changed

2013-12-05 Thread Pawel Veselov
On Wed, Dec 4, 2013 at 11:45 PM, joris dedieu joris.ded...@gmail.comwrote: 2013/12/2 Pawel Veselov pawel.vese...@gmail.com: Maybe an external library like ldns http://www.nlnetlabs.nl/projects/ldns/, may provide a complete protocole handeling (resolv.conf parsing, dns query, packet parsing,

Re: make haproxy notice that backend server ip has changed

2013-12-04 Thread joris dedieu
2013/12/2 Pawel Veselov pawel.vese...@gmail.com: Here is my first attempt at this: http://pastebin.com/xXfZJf3f The diff is over http://git.1wt.eu/git/haproxy-1.4.git/ ref eb9632f7c6ae675bdee4c82eb0d298ba7f37fc52 To enable DNS checks on a server, the host name defined configuration should

Re: make haproxy notice that backend server ip has changed

2013-12-02 Thread Pawel Veselov
Here is my first attempt at this: http://pastebin.com/xXfZJf3f The diff is over http://git.1wt.eu/git/haproxy-1.4.git/ref eb9632f7c6ae675bdee4c82eb0d298ba7f37fc52 To enable DNS checks on a server, the host name defined configuration should be suffixed with @ar, and checks must be enabled for

Re: make haproxy notice that backend server ip has changed

2013-11-23 Thread Eugene Istomin
Willy, such a great idea! We can help in testing. -- */Best regards,/* /Eugene Istomin/ Hi Pawel, On Fri, Nov 22, 2013 at 07:54:18PM -0800, Pawel Veselov wrote: Hi. There has been a heated discussion on this about 2 years back, so sorry for reopening any wounds. Also sorry for

Re: make haproxy notice that backend server ip has changed

2013-11-23 Thread Steven Le Roux
Going further on this, it would be amazing to have the hability to plug haproxy with zookeeper for service discovering and health checks. Since zk use an application aware heartbeat, it maintains a connection to perform health checks. If a service is noticed as down, the ephemeral znode will be

Re: make haproxy notice that backend server ip has changed

2013-11-23 Thread Pawel Veselov
Hi Willy, On Sat, Nov 23, 2013 at 1:38 AM, Willy Tarreau w...@1wt.eu wrote: Hi Pawel, On Fri, Nov 22, 2013 at 07:54:18PM -0800, Pawel Veselov wrote: Hi. There has been a heated discussion on this about 2 years back, so sorry for reopening any wounds. Also sorry for long winded intro.

Re: make haproxy notice that backend server ip has changed

2011-08-06 Thread Willy Tarreau
On Sat, Aug 06, 2011 at 02:42:45AM +0300, Piavlo wrote: Well certainly aws has it's limitations which force you to design a very different infrastructure than you would in normal datacenter environment. IMHO this is the great thing about those limitations as you are forced to start

Re: make haproxy notice that backend server ip has changed

2011-08-05 Thread Piavlo
On 08/05/2011 06:51 AM, Julien Vehent wrote: On Fri, 05 Aug 2011 01:08:22 +0300, Piavlo wrote: Hi Jens, I'm using names which resolve to internal EC2 addresses in haproxy configs - the /etc/hosts of all instances are auto updated then new instance is added/removed. But the problem manifests

Re: make haproxy notice that backend server ip has changed

2011-08-05 Thread Piavlo
On 08/05/2011 06:53 PM, Willy Tarreau wrote: On Fri, Aug 05, 2011 at 11:17:16AM +0300, Piavlo wrote: But why do a reload of haproxy in other situations (much more common in my use case and loose statistics and possibly some connections) if there could be a config option that tells haproxy to

Re: make haproxy notice that backend server ip has changed

2011-08-05 Thread Baptiste
Why don't you edit the haproxy conf directly and reload it ? If you have the new IP and are going to update the /etc/hosts, what is stopping you from doing a sed on the backend's ip in haproxy.cfg ? Or, you could just run in a VPC and stop doing weird stuff with your networking ;) Julien

Re: make haproxy notice that backend server ip has changed

2011-08-05 Thread Willy Tarreau
Hi Julien, On Fri, Aug 05, 2011 at 05:07:36PM -0400, Julien Vehent wrote: Willy: EC2 gives a different kind of flexibility but requires to think differently. So, yeah, they do crazy stuffs like randomizing the LAN IPs allocations. But people have been complaining about that so much that

Re: make haproxy notice that backend server ip has changed

2011-08-05 Thread Baptiste
On Fri, Aug 5, 2011 at 11:58 PM, Willy Tarreau w...@1wt.eu wrote: Hi Baptiste, On Fri, Aug 05, 2011 at 11:53:40PM +0200, Baptiste wrote: Or using some kind of haproxy conf template with some keyword you replace using sed with IPs you would get from the hosts file? with inotify, you can get

Re: make haproxy notice that backend server ip has changed

2011-08-05 Thread Piavlo
Well certainly aws has it's limitations which force you to design a very different infrastructure than you would in normal datacenter environment. IMHO this is the great thing about those limitations as you are forced to start thinking differently and end up using a set of well known and

make haproxy notice that backend server ip has changed

2011-08-04 Thread Piavlo
Hi, I'm running haproxy in ec2 environment - and there is one problem I noticed. The backend servers are configured as names and not ip - if backend server IP changes and even if the /etc/hosts on haproxy server is updated - haproxy does not catch this change. It has to be restarted to catch

Re: make haproxy notice that backend server ip has changed

2011-08-04 Thread Piavlo
Hi Jens, I'm using names which resolve to internal EC2 addresses in haproxy configs - the /etc/hosts of all instances are auto updated then new instance is added/removed. But the problem manifests then the instance is stoped and then started - this makes the internal ip to change. I can also

Re: make haproxy notice that backend server ip has changed

2011-08-04 Thread Julien Vehent
On Fri, 05 Aug 2011 01:08:22 +0300, Piavlo wrote: Hi Jens, I'm using names which resolve to internal EC2 addresses in haproxy configs - the /etc/hosts of all instances are auto updated then new instance is added/removed. But the problem manifests then the instance is stoped and then started -

Re: make haproxy notice that backend server ip has changed

2011-08-04 Thread Willy Tarreau
On Fri, Aug 05, 2011 at 01:08:22AM +0300, Piavlo wrote: Hi Jens, I'm using names which resolve to internal EC2 addresses in haproxy configs - the /etc/hosts of all instances are auto updated then new instance is added/removed. But the problem manifests then the instance is stoped and