[MXS-4670] The fact that readconnroute doesn't block writes with router_options=slave is not documented Created: 2023-07-12 Updated: 2023-10-09 Resolved: 2023-07-13 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Documentation |
| Affects Version/s: | 2.5.26, 23.02.2 |
| Fix Version/s: | 2.5.27 |
| Type: | Bug | Priority: | Major |
| Reporter: | Bryan Bancroft (Inactive) | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | triage | ||
| Environment: |
ec2 |
||
| Description |
|
The fact that readconnroute will happily route writes to replicas with router_options=slave is not documented. This should be clearly stated in the documentation since one might assume that writes would be blocked. Original description: Issue; If I define a read-only service As a super user I can still write to a replica. This allows certain users to break an async cluster thru the RO service Expectation; If connecting to a RO service, regardless of user, writes should be blocked
|
| Comments |
| Comment by markus makela [ 2023-07-12 ] | |||||||
|
If this is a readconnroute service with router_options=slave then this is by design. Determining whether a query is a write or not would require parsing it and readconnroute is designed to not require parsing. This isn't explicitly documented for the readconnroute but it can sort of be deduced from the fact that it only has one connection. | |||||||
| Comment by Bryan Bancroft (Inactive) [ 2023-07-12 ] | |||||||
|
markus makela I spoke to Todd and we talked about the same. If a know limitation we need to document this as it is counter intuitive | |||||||
| Comment by markus makela [ 2023-07-12 ] | |||||||
|
I'll add the following to the readconnroute documentation:
|