From 9d11bc4ba7d5b752ab8da4ff45f82da084a0145a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ren=C3=A9=20Canna=C3=B2?= Date: Sun, 24 Jul 2016 09:30:58 +0000 Subject: [PATCH] Updating documentation on Monitor connection pool --- doc/monitor.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/monitor.md b/doc/monitor.md index 06ccb1a4c..0827375a2 100644 --- a/doc/monitor.md +++ b/doc/monitor.md @@ -110,4 +110,8 @@ Version v1.2.1 tries to overcome this limitation with a new implementation. Now: * *Monitor* initializes a Thread Pool of workers and creates a queue; * *monitor_connect_thread*, *monitor_ping_thread*, *monitor_read_only_thread* and *monitor_replication_lag_thread* are producers that generate tasks and sent them to the workers using the queue; * the workers process the tasks and perform the requires actions; -* if *Monitor* detects that the queue is growing too fast, it creates new temporary worker threads +* if *Monitor* detects that the queue is growing too fast, it creates new temporary worker threads + +Connection purging +================== +Monitor implements its own connection pool. Connections that are alive for more than 3 * `mysql_thread___monitor_ping_interval` milliseconds are automatically purged