[MXS-1889] A single remaining master is valid for readconnroute configured with 'router_options=slave' Created: 2018-05-30  Updated: 2020-08-25  Resolved: 2018-06-01

Status: Closed
Project: MariaDB MaxScale
Component/s: readconnroute
Affects Version/s: 2.1.13, 2.1.14, 2.1.15, 2.1.16, 2.1.17, 2.2
Fix Version/s: 2.2.8

Type: Bug Priority: Major
Reporter: Johan Wikman Assignee: Johan Wikman
Resolution: Fixed Votes: 1
Labels: None


 Description   

With a configuration like

[SomeService]
type=service
router=readconnroute
router_options=slave

readconnroute will still select a master if that is the only server that is left.

However, later, from 2.1.13 onwards, when readconnroute asseses in connection_is_valid() whether the connection is valid, it will reject it and thus the client will get no connection.



 Comments   
Comment by Geoff Montee (Inactive) [ 2018-05-30 ]

As part of this, I would also suggest updating the documentation. For router_options=slave, it currently says:

slave A server assigned as a slave of a master.

This should probably be clarified to something like the following:

slave A server assigned as a slave of a master. If all slaves are down, but the master is still available, then the router will use the master.

https://mariadb.com/kb/en/mariadb-enterprise/mariadb-maxscale-22-readconnroute/#router-options

Generated at Thu Feb 08 04:10:09 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.