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

Update schema router documentation

Browse Source
This commit is contained in:
Johan Wikman
2018-10-03 16:15:29 +03:00
parent 9ecd027ea0
commit 4a01410742
3 changed files with 32 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
Documentation/Changelog.md
View File

@ -21,6 +21,7 @@
* Transaction load balancing for normal transactions * Transaction load balancing for normal transactions
* Support for runtime router reconfiguration * Support for runtime router reconfiguration
* Experimental resultset concatenation router, `cat` * Experimental resultset concatenation router, `cat`
* The schema router is now capable of sharding tables.
For more details, please refer to: For more details, please refer to:

5
Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md
View File

@ -205,6 +205,11 @@ for details.
The `source` parameter can now contain a list of comma separated addresses. The `source` parameter can now contain a list of comma separated addresses.
### Table Sharding
The SchemaRouter is now capable of sharding tables. Please see the SchemaRouter
[documentation](../Routers/SchemaRouter.md) for details.
### Interactive Mode for MaxCtrl ### Interactive Mode for MaxCtrl
### ReadWriteSplit ### ReadWriteSplit

26
Documentation/Routers/SchemaRouter.md
View File

@ -8,6 +8,9 @@ database-based sharding, the schemarouter router also enables cross-node
session variable usage by routing all queries that modify the session to all session variable usage by routing all queries that modify the session to all
nodes. nodes.
From 2.3.0 onwards, the SchemaRouter is capable of sharding tables, in
addition to sharding databases.
## Routing Logic ## Routing Logic
If a command line client is used, i.e. `mysql`, and a direct connection to If a command line client is used, i.e. `mysql`, and a direct connection to
@ -114,6 +117,29 @@ refresh_databases=true
refresh_interval=60 refresh_interval=60
``` ```
## Table Sharding
This functionality was introduced in 2.3.0.
If the same database exists on multiple servers, but the database contains
different tables in each server, the SchemaRouter is capable of
transparently routing queries to the right server, depending on which table
is being addressed.
For instance, suppose the database `db` exists on servers _server1_ and
_server2_, but that the database on _server1_ contains the table `tbl1` and
on _server2_ contains the table `tbl2`.
In that case, the query
```
SELECT * FROM db.tbl1
```
will be routed to _server1_ and the query
```
SELECT * FROM db.tbl2
```
will be routed to _server2_.
## Router Options ## Router Options
**Note:** Router options for the Schemarouter were deprecated in MaxScale 2.1. **Note:** Router options for the Schemarouter were deprecated in MaxScale 2.1.