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

Merge branch '2.4.0' into 2.4

Browse Source
This commit is contained in:
Johan Wikman 2019-06-25 11:43:08 +03:00
commit 1b5071260b
2 changed files with 27 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Documentation/Changelog.md
View File

@ -2,6 +2,11 @@
## MariaDB MaxScale 2.4
* A Clustrix specific monitor has been added.
* A new router, Smart Router, capable of routing a query to different
backends depending on the characteristics of the query has been added.
* Transaction replaying is now performed also in conjunction with server
initiated transaction rollbacks.
* Names starting with `@@` are reserved for use by MaxScale.
* Names can no longer contain whitespace.
* Servers can now be drained.

22
Documentation/Release-Notes/MaxScale-2.4.0-Release-Notes.md
View File

@ -83,6 +83,23 @@ what it used to do.
## New Features
### Clustrix Support
MaxScale now contains support for Clustrix in the form of a Clustrix monitor
that is capable of monitoring a Clustrix cluster.
Please see the
[documentation](../Monitors/Clustrix-Monitor.md) for details.
### Smart Router
MaxScale has now a new router _SmartRouter_ that is capable of routing a query
to different kinds of backends, containing the same data, depending on which
backend can best handle that particular kind of query.
Please see the
[documentation](../Routers/SmartRouter.md) for details.
### Servers can be drained
It is now possible to drain a server, which means that existing
@ -181,6 +198,11 @@ the `set` endpoint.
For more information on the readwritesplit router, refer to the
[documentation](../Routers/ReadWriteSplit.md).
#### `transaction_replay`
The transaction replay functionality will now also be applied in conjunction
with server initiated transaction rollbacks.
#### `transaction_replay_attempts`
The new `transaction_replay_attempts` parameter controls how many errors the