[MXS-636] Continue handling read queries although master is lost Created: 2016-03-23 Updated: 2016-05-03 Resolved: 2016-05-03 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readwritesplit |
| Affects Version/s: | 1.4.0 |
| Fix Version/s: | 2.0.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Rasmus Johansson (Inactive) | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | 2016-8 | ||||||||
| Description |
|
MaxScale's ReadWrite router stops processing any queries if the connection to the master is lost. It has been requested that MaxScale could/should continue processing read queries by sending them to the slaves and only stop write queries (DDL and DML) by returning an error indicating that the master is down. |
| Comments |
| Comment by Johan Wikman [ 2016-03-23 ] |
|
I think this is a duplicate and may actually have been fixed already. markus makela, could you comment. |
| Comment by markus makela [ 2016-03-23 ] |
|
I couldn't find an open bug for this so this was created. |