From b06d9830ae0026b72e72d82ec6e685df9ae3a1e8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= Date: Wed, 10 Oct 2018 01:02:13 +0300 Subject: [PATCH] Extend ADAPTIVE_ROUTING in release notes Added a link and made the description more uniform with the rest of the document. Also made the description slightly simpler so that it's easier to understand. --- .../Release-Notes/MaxScale-2.3.0-Release-Notes.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md index 4a6298944..0adfb6a5f 100644 --- a/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md @@ -279,9 +279,12 @@ transactions (i.e. `START TRANSACTION` or `BEGIN`) are load balanced across slaves. If the transaction tries to modify a row, it is migrated to the master and rolled back on the slave. -#### 'Adaptive Routing' -A new load balancing method. Server load conditions are proxied by measuring -query response times for each server. +#### Adaptive Routing + +A new load balancing method, +[`ADAPTIVE_ROUTING`](../Routers/ReadWriteSplit.md#slave_selection_criteria), was +added. It uses the average query response time to distribute the load so that it +is optimal on all servers. ### MaxCtrl