[MXS-2421] maxctrl stops working with ESOCKETTIMEDOUT Created: 2019-04-03 Updated: 2020-06-03 Resolved: 2019-04-18 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | maxctrl |
| Affects Version/s: | 2.3.4 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Claudio Nanni | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | need_feedback | ||
| Description |
|
maxctrl stops working after trying a switchover:
|
| Comments |
| Comment by markus makela [ 2019-04-03 ] |
|
This is likely to be fixed by 2.3.5 where the monitor does less locking. |
| Comment by markus makela [ 2019-04-15 ] |
|
This is not really a bug: the default value of --timeout is 10 seconds and if a failover takes longer than that, the connection is closed. The failover will still proceed but the client won't know. To fix this, increase the timeout to a larger value. |
| Comment by Claudio Nanni [ 2019-04-15 ] |
|
Why would:
Also timeout? |
| Comment by markus makela [ 2019-04-16 ] |
|
The command requires data from the monitor to get the GTID values for each server. In 2.3.4, the monitor holds the lock that protects the GTID values for the duration of the failover whereas in 2.3.5 the lock is only held while the values are being updated. |