Nenad Merdanovic 174dd37d88 MINOR: Add ability for agent-check to set server maxconn ... This is very useful in complex architecture systems where HAproxy is balancing DB connections for example. We want to keep the maxconn high in order to avoid issues with queueing on the LB level when there is slowness on another part of the system. Example is a case of an architecture where each thread opens multiple DB connections, which if get stuck in queue cause a snowball effect (old connections aren't closed, new ones cannot be established). These connections are mostly idle and the DB server has no problem handling thousands of them. Allowing us to dynamically set maxconn depending on the backend usage (LA, CPU, memory, etc.) enables us to have high maxconn for situations like above, but lowering it in case there are real issues where the backend servers become overloaded (cache issues, DB gets hit hard).		2016-04-25 17:23:50 +02:00
..
common	CLEANUP: chunk: adding NULL check to chunk_dup allocation.	2016-03-24 10:18:44 +01:00
import	MINOR: lru: new function to delete <nb> least recently used keys	2016-01-11 07:31:35 +01:00
proto	MINOR: Add ability for agent-check to set server maxconn	2016-04-25 17:23:50 +02:00
types	MINOR: filters: Print the list of existing filters during HA startup	2016-04-21 06:58:08 +02:00