Now, there is a completely separate check where OS talks to OS (without touching the app or haproxy): ![]() These options were for haproxy talking to application. Similarly, set timeout server for the backend. This is bad because the number of connections isn't infinite ( maxconn). You can always have an application that occupies a connection but doesn't speak to you. The timeout client detects a dead client application on a responsive client OS. Then I've started wireshark and sniffed all the tcp traffic: after the last request from the clients, the tcp keepalived packets are sente regularly after 120 seconds, but after 200 seconds after the last request from the clients the connection are closed (thus ignoring the keepalived packet). In HAProxy I've setted timeout client/server to 200 seconds (>120 seconds of the keepalive packets) and used the option clitcpka. ![]() I've changed the client and server TCP keepalive timeout, setting _keepalive_time=120 (CentOS 7). The clients create and use permanent connection to the AMQP Servers, via HAProxy. ![]() I have configured HAProxy (1.5.4, but I tried also 1.5.14) to balance in TCP mode two server exposing AMQP protocol (WSO2 Message Broker) on 5672 port.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |