[MXS-1177] Configurable monitor check failures Created: 2017-03-08  Updated: 2017-12-01  Resolved: 2017-04-03

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: None
Fix Version/s: 2.2.0

Type: New Feature Priority: Major
Reporter: Guillaume Lefranc Assignee: Esa Korhonen
Resolution: Fixed Votes: 1
Labels: None

Sprint: 2017-31

 Description   

It would be great to have configurable monitor check failures in MaxScale, especially when we want to put the monitor_interval to a low value. Right now if a monitor fails a check it marks the server as down as soon as the check is failed.

I envision something similar as ProxySQL has:

If a host misses mysql-monitor_ping_max_failures pings in a row, MySQL_Monitor informs MySQL_Hostgroup_Manager that the node is unreacheable and that should immediately kill all connections. It is important to note that in case a connection to the backend is not available, MySQL_Monitor will first try to connect in order to ping, therefore the time to detect a node down could be one of the two:

mysql-monitor_ping_max_failures * mysql-monitor_connect_timeout
mysql-monitor_ping_max_failures * mysql-monitor_ping_timeout

A monitor_max_failures parameter with a default of 1 would be an improvement of this feature.



 Comments   
Comment by Esa Korhonen [ 2017-04-03 ]

The monitor parameter name to control this feature is "backend_connect_attempts".

Generated at Thu Feb 08 04:04:47 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.