[MXS-1950] No explanation for routing failure when no valid servers are available Created: 2018-06-30 Updated: 2018-07-24 Resolved: 2018-07-03 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readwritesplit |
| Affects Version/s: | 2.2.10 |
| Fix Version/s: | 2.2.11 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
If MaxScale is configured with master_failure_mode=fail_on_write and the session has no active master connection, a loss of the slave status will cause a routing failure. The routing failure is logged by the protocol module but no additional details are provided by readwritesplit. |