babcda3eca
2.4.12 Update Change Date
2020-08-24 09:42:48 +03:00
fc9c9fcd77
2.4.11 Update change date
2020-07-07 10:01:38 +03:00
5ebae9be90
Merge branch '2.3' into 2.4
2020-06-05 09:36:24 +03:00
d3d7054639
Merge branch '2.3' into 2.4
2020-04-24 16:09:20 +03:00
d0ab797938
Merge branch '2.3' into 2.4
2020-03-12 10:33:57 +02:00
8b763fb88b
Merge branch '2.3' into 2.4
2020-02-12 08:27:48 +02:00
a7e0142224
Merge branch '2.3' into 2.4
2020-01-15 11:29:37 +02:00
a9a2b753c0
Update 2.4.5 change date
2019-12-18 13:25:03 +02:00
f6731a898d
Update change date
2019-11-13 08:37:17 +02:00
fdfbf3e133
Update 2.4.3 change date
2019-11-05 12:21:00 +02:00
861e27eb00
Merge branch '2.3' into 2.4
2019-10-29 14:04:31 +02:00
0ba779d5a2
Update 2.4.0 Change Date
2019-06-25 10:11:55 +03:00
8fa8181009
MXS-2540 Use new conf. mech. in Clustrix monitor
2019-06-05 11:10:28 +03:00
418ccf861d
Format routers and monitors
2019-05-10 10:31:12 +03:00
e09a6c8100
MXS-2428 Add 'dynamic_node_detection' 'health_check_port'
...
'dynamic_node_detection' specifies whether the Clustrix monitor
should dynamically figure out what nodes there are, or just rely
upon static information.
'health_check_port' specifies the port to be used when perforing
the health check ping.
2019-04-16 13:58:27 +03:00
89c059411d
MXS-2219 Add health check threshold
...
Make it configurable how many times a node may fail to respond
on the health check port before it is considered to be down.
2019-01-17 11:11:21 +02:00
4512295e40
MXS-2219 Implement rudimentary Clustrix monitoring
...
The monitor now pings the health check ports of the Clustrix nodes.
A response translates to RUNNING and a non-response to DOWN.
2019-01-07 12:59:27 +02:00
115feab946
MXS-2164 Add skeleton Clustrix monitor
2018-12-18 15:17:09 +02:00
