[MXS-2144] Doing a controlled shutdown doesn't trigger query retrying Created: 2018-11-06 Updated: 2018-11-15 Resolved: 2018-11-15 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readwritesplit |
| Affects Version/s: | 2.3.0 |
| Fix Version/s: | 2.3.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-70 |
| Description |
|
When a query is interrupted by a server shutdown, it won't get retried as it appears to the router like any normal error (e.g. a syntax error). This can be worked around by putting the server first into maintenance mode and then shutting the server down. One way of dealing with this is to inspect the returned packet in RWBackend::process_reply and store the error type. If the correct error is found a fake hangup event on the DCB could be created and the normal error handling would take care of the retrying. |
| Comments |
| Comment by Dipti Joshi (Inactive) [ 2018-11-08 ] |
|
johan.wikman, markus makela Is this scheduled for 2.3.1? |
| Comment by Johan Wikman [ 2018-11-09 ] |
|
It would seem to me that shutting down a server in a controlled manner, is exactly what the MaxScale maintenance mode is intended for. |