From ef53ac064d30afde810ee897b0344bf5a10e6e77 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Wed, 22 Apr 2015 20:58:52 +0300 Subject: [PATCH 1/4] Added maximum session command amount for schemarouter. --- routers/schemarouter/SchemaRouter.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/routers/schemarouter/SchemaRouter.md b/routers/schemarouter/SchemaRouter.md index f583ab357..7823bd817 100644 --- a/routers/schemarouter/SchemaRouter.md +++ b/routers/schemarouter/SchemaRouter.md @@ -42,6 +42,12 @@ GRANT SELECT,USAGE ON shard.* TO 'john'@'%'; This would in effect allow the user 'john' to only see the database 'shard' on this server. Take notice that these grants are matched against MaxScale's hostname instead of the client's hostname. Only user authentication uses the client's hostname and all other grants use MaxScale's hostname. +The schemarouter supports the following router options: + +|option |parameter |description| +--------------------------------------------- +|max_sescmd_hitory | |Set a limit on the number of session modifying commands a session can execute. This sets an effective cap on the memory consupmtion of the session.| + ## Limitations The schemarouter router currently has some limitations due to the nature of the sharding implementation and the way the session variables are detected and routed. Here is a list of the current limitations. From 675ecd7e2d95cc38ea578283eab43591c2f4e211 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Thu, 23 Apr 2015 15:04:38 +0300 Subject: [PATCH 2/4] Updated documentation and added a message if libedit is not found. --- About/About-MaxScale.md | 4 ++-- Changelog.md | 8 ++++++++ 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/About/About-MaxScale.md b/About/About-MaxScale.md index d2d133414..4477c2907 100644 --- a/About/About-MaxScale.md +++ b/About/About-MaxScale.md @@ -13,8 +13,8 @@ A Google Group exists for MaxScale that can be used to discuss ideas, issues and Send email to [maxscale@googlegroups.com](mailto:maxscale@googlegroups.com) or use the [forum](http://groups.google.com/forum/#!forum/maxscale) interface -Bugs can be reported in the MariaDB Corporation bugs database - [bug.mariadb.com](http://bugs.mariadb.com) +Bugs can be reported in the MariaDB Jira + [https://mariadb.atlassian.net](https://mariadb.atlassian.net) ## Installing MaxScale Information about installing MaxScale, either from a repository or by building from source code, is included in the guide [Getting Started with MaxScale](/Documentation/Getting-Started/Getting-Started-With-MaxScale.md). diff --git a/Changelog.md b/Changelog.md index 9716d0eed..c33b38a00 100644 --- a/Changelog.md +++ b/Changelog.md @@ -2,6 +2,14 @@ These are the changes introduced in the next MaxScale version. This is not the official change log and the latest changelog can always be found in here: [MaxScale 1.1 Release Notes](Release-Notes/MaxScale-1.1-Release-Notes.md) +## MaxScale 1.1.1 + +* Schemarouter now also allows for an upper limit to session commans. +* Schemarouter correctly handles SHOW DATABASES responses that span multiple buffers. +* Logfiles have been renamed. The log names are now named error.log, messages.log, trace.log and debug.log. + +## MaxScale 1.1 + **NOTE:** MaxScale default installation directory has changed to `/usr/local/mariadb-maxscale` and the default password for MaxAdmin is now ´mariadb´. * New modules added From 2a35ed1c47d300b0a19d7fda0a29482c8158301a Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Thu, 23 Apr 2015 21:05:50 +0300 Subject: [PATCH 3/4] Updated documentation. --- Changelog.md | 3 +++ Getting-Started/Configuration-Guide.md | 2 ++ 2 files changed, 5 insertions(+) diff --git a/Changelog.md b/Changelog.md index c33b38a00..fa20383ac 100644 --- a/Changelog.md +++ b/Changelog.md @@ -6,8 +6,11 @@ These are the changes introduced in the next MaxScale version. This is not the o * Schemarouter now also allows for an upper limit to session commans. * Schemarouter correctly handles SHOW DATABASES responses that span multiple buffers. +* Schemarouter now allows disabling of the session command history. +* Readwritesplit now allows disabling of the session command history. * Logfiles have been renamed. The log names are now named error.log, messages.log, trace.log and debug.log. + ## MaxScale 1.1 **NOTE:** MaxScale default installation directory has changed to `/usr/local/mariadb-maxscale` and the default password for MaxAdmin is now ´mariadb´. diff --git a/Getting-Started/Configuration-Guide.md b/Getting-Started/Configuration-Guide.md index 8b3fdc301..5ce081a82 100644 --- a/Getting-Started/Configuration-Guide.md +++ b/Getting-Started/Configuration-Guide.md @@ -823,6 +823,8 @@ In above-mentioned case the user-defined variable would only be updated in the m When a limitation is set, it effectively creates a cap on the session's memory consumption. This might be useful if connection pooling is used and the sessions use large amounts of session commands. +`disable_sescmd_history=true|false` disables the session command history. This way nothing is stored and if a slave server fails and a new one is taken in its stead, the session on that server will be in an inconsistent state compared to the master server. Disabling session command history will allow connection pooling without causing a constant growth in the memory consumption. + An example of Read/Write Split router configuration : ``` From a11bc4c3454bcde9e0ad4aa719bfd0489db40089 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Fri, 24 Apr 2015 06:19:50 +0300 Subject: [PATCH 4/4] Added README.md and updated schemarouter documentation. --- routers/schemarouter/SchemaRouter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/routers/schemarouter/SchemaRouter.md b/routers/schemarouter/SchemaRouter.md index 7823bd817..d1de66b2b 100644 --- a/routers/schemarouter/SchemaRouter.md +++ b/routers/schemarouter/SchemaRouter.md @@ -47,7 +47,7 @@ The schemarouter supports the following router options: |option |parameter |description| --------------------------------------------- |max_sescmd_hitory | |Set a limit on the number of session modifying commands a session can execute. This sets an effective cap on the memory consupmtion of the session.| - +|disable_sescmd_history||Disable the session command history. This will prevent growing memory consumption of a long-running session and allows pooled connections to MaxScale to be used. The drawback of this is the fact that if a server goes down, the session state will not be consistent anymore.| ## Limitations The schemarouter router currently has some limitations due to the nature of the sharding implementation and the way the session variables are detected and routed. Here is a list of the current limitations.