[MXS-1417] draining a node should be possible like haproxy does Created: 2017-09-15 Updated: 2018-05-23 Resolved: 2018-05-23 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | maxctrl |
| Affects Version/s: | 2.1.7 |
| Fix Version/s: | 2.3.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Oli Sennhauser | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Environment: |
linux ubuntu 14.04 n.a |
||
| Sprint: | MXS-SPRINT-58 |
| Description |
|
set server xxx maintenance causes existing connections to abort. it would be much nicer to have a set server xxx drain as haproxy does see irc conversions with markus (09:04:57) shinguz: does MaxScale 2.1 really not allow draining a node as HAproxy does? |
| Comments |
| Comment by Oli Sennhauser [ 2017-09-15 ] |
|
removing a server as markus suggested does not help and shows the same ugly behaviour... root@mariadb-10.2 [(none)] SQL> SELECT @@hostname, @@wsrep_node_name; |
| Comment by markus makela [ 2017-09-16 ] |
|
The behavior described above is caused by |
| Comment by Brad Jorgensen [ 2017-09-22 ] |
|
I am running maxscale 2.1.8 and this is still happening to me. |
| Comment by markus makela [ 2017-09-23 ] |
|
bradjorgensen do you mean that setting servers into maintenance closes all active connections? This is still expected as |
| Comment by markus makela [ 2018-03-26 ] |
|
This could be implemented as a MaxCtrl command: maxctrl drain server <name> This command would remove the server from all services and wait until the connection count drops to zero. After this, it could set the server into maintenance mode and add it back to the services. |