Now, you can simply use whatever tool (ab, httperf, wrk, etc...) hosted on a third party VM to inject traffic on ELB IP directly. After a few minutes (less than 5), ELB service will be moved automatically to an other instance, leading IP to change. On HAProxy stat socket, you should see the 'update' counter to be incremented to 1. Of course, traffic load-balanced by HAProxy should followup as well.
Baptiste On Wed, Oct 28, 2015 at 2:05 PM, Ben Tisdall <ben.tisd...@photobox.com> wrote: > On Wed, Oct 28, 2015 at 1:55 PM, Baptiste <bed...@gmail.com> wrote: > >> >> Have you forced resolution to ipv4 only? >> if not, could you give it a try? >> > > Right, with "resolver-prefer ipv4": > > Resolvers section aws > nameserver aws_0: > sent: 11 > valid: 11 > update: 0 > cname: 0 > cname_error: 0 > any_err: 0 > nx: 0 > timeout: 0 > refused: 0 > other: 0 > invalid: 0 > too_big: 0 > truncated: 0 > outdated: 0
