On Mon, Aug 03, 2015 at 08:16:48AM +0000, [email protected] wrote: > Dear Willy, > > > Thank you for the quick response. I wasn???t interested in some specific TCP > option. I was interested in differentiation of HAProxy heartbeat handshakes > from client request tcp handshakes while connecting to the backend server. > So, allowing any option to be forwarded to backend server would do the trick.
Normally you want them to be the same otherwise you can end up with a check that works and prod traffic that doesn't work. > Up till now I have thought about using (A) transparent proxy mode, (B) > separate IP for heartbeat and separate IP for client request or (C) separate > port for heartbeat and separate list of ports for client reuqest. However, in > option (A) it isn???t possible to load balance traffic from the same subnet, > option (B) is the best option I have so far but it requires an additional IP > to be allocated to HAProxy and option (C) would limit the number of > concurrent connections per backend server. You can also use the "addr" parameter to force to send health checks to a different IP address. That may fit your needs. Other people simply use a different method in the health check that is not logged. That's why the default method is OPTIONS. Regards, Willy
