hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

MXS-1752: Clarify router behavior

Browse Source 
Amended the documentation to specify the exact behavior of the router when
non-resultset results are returned.
This commit is contained in:
Markus Mäkelä 2018-04-24 11:56:22 +03:00
parent 88ae276dd6
commit 2cfa66ff7d
No known key found for this signature in database
GPG Key ID: 72D48FCE664F7B19
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/Routers/Cat.md
View File

@ -15,8 +15,12 @@ parameter of the service. The result will only be completed once all servers
have executed this.
All commands executed via this router will be executed on all servers. This
means that an INSERT through the `cat` router will send it to all servers. As
the intended use-case of the router is to mainly reduce multiple result sets
means that an INSERT through the `cat` router will send it to all servers. In
the case of commands that do not return resultsets, the response of the last
server is sent to the client. This means that if one of the earlier servers
returns a different result, the client will not see it.
As the intended use-case of the router is to mainly reduce multiple result sets
into one, it has no mechanisms to prevent writes from being executed on slave
servers (which would cause data corruption or replication failure). Take great
care when performing administrative operations though this router.