[MXS-1711] transfer threads to other server upon server failure Created: 2018-03-07 Updated: 2019-03-04 Resolved: 2019-03-04 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readconnroute |
| Affects Version/s: | 2.1.13, 2.2.2 |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Major |
| Reporter: | Kyle Joiner (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Description |
|
When using the ReadConnRouter and a server drops all connections that were using that server are dropped. Please provide a means that will allow for the connection to error on the current query then be automatically moved to another operating server. |
| Comments |
| Comment by markus makela [ 2018-05-25 ] |
|
Adding support for this would mean that all queries must be parsed to know which change the session state. This would remove any benefit of using readconnroute over readwritesplit so if such behavior is needed, one would be better off using readwritesplit. Less efficient options would include storing all executed queries and replaying them in case the connection closes as well as reconnecting regardless of the session state. |
| Comment by Johan Wikman [ 2018-07-04 ] |
|
Actually, on a second thought, I think it would be a mistake to make this kind of change. The point of ReadConnRoute is that it is simple and it should kept that way. As markus makela says, if something more advanced is needed, it is better to switch to ReadWriteSplit. |
| Comment by markus makela [ 2019-03-04 ] |
|
Due to the extremely limited use of this feature, and the possibly dangerous side-effects of a naive implementation, we won't implement this. The enhancements made to readwritesplit in 2.3 further make this feature less attractive to implement. |