From bb4eb39d8b1b9706da6b30fd482139c80f67845d Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Mon, 11 May 2015 09:11:25 +0300 Subject: [PATCH 01/10] Updated release notes. --- Release-Notes/MaxScale-1.1.1-Release-Notes.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Release-Notes/MaxScale-1.1.1-Release-Notes.md b/Release-Notes/MaxScale-1.1.1-Release-Notes.md index 9ccf7b930..0bcfe95d5 100644 --- a/Release-Notes/MaxScale-1.1.1-Release-Notes.md +++ b/Release-Notes/MaxScale-1.1.1-Release-Notes.md @@ -42,7 +42,8 @@ Here is a list of bugs fixed since the release of the 1.1 version of MaxScale. T |[MXS-33](https://mariadb.atlassian.net/browse/MXS-33)|bugzillaId-702: CLI: list services command shows negative values for the number of users of a service (Read Service).| |[MXS-17](https://mariadb.atlassian.net/browse/MXS-17)|bugzillaId-736: Memory leak while doing read/write splitting| |[MXS-30](https://mariadb.atlassian.net/browse/MXS-30)|bugzillaId-487: Buffer manager should not use pointer arithmetic on void*| - +|[MXS-81](https://mariadb.atlassian.net/browse/MXS-81)|cmake fails when init scripts are missing| +|[MXS-127](https://mariadb.atlassian.net/browse/MXS-127)|disable_sescmd_history causes MaxScale to crash under load| ## Known Issues There are a number bugs and known limitations within this version of MaxScale, the most serious of this are listed below. From 705c4e5a0523e344c6dee5fad878a7bca1ca3caa Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Mon, 11 May 2015 09:26:45 +0300 Subject: [PATCH 02/10] Changed from tables to bullets in bug lists. --- Release-Notes/MaxScale-1.1.1-Release-Notes.md | 43 +++++++++---------- 1 file changed, 21 insertions(+), 22 deletions(-) diff --git a/Release-Notes/MaxScale-1.1.1-Release-Notes.md b/Release-Notes/MaxScale-1.1.1-Release-Notes.md index 0bcfe95d5..47edcb6c3 100644 --- a/Release-Notes/MaxScale-1.1.1-Release-Notes.md +++ b/Release-Notes/MaxScale-1.1.1-Release-Notes.md @@ -22,28 +22,27 @@ Using the password functionality in MaxScale is now a lot easier. Both programs Here is a list of bugs fixed since the release of the 1.1 version of MaxScale. The bug IDs are from the **[Mariadb Jira](https://mariadb.atlassian.net/)**. -|Bug|Description| -|---|-----------| -|[MXS-99](https://mariadb.atlassian.net/browse/MXS-99)|/etc/init.d/maxscale reload doesn't do anything| -|[MXS-83](https://mariadb.atlassian.net/browse/MXS-83)|linkage fails when system pcre library is recent| -|[MXS-112](https://mariadb.atlassian.net/browse/MXS-112)|Disable saving of session commands in the readwritesplit and schemarouter modules| -|[MXS-114](https://mariadb.atlassian.net/browse/MXS-114)|Disable recovery of disconnected slaves| -|[MXS-73](https://mariadb.atlassian.net/browse/MXS-73)|MaxScale uses nearly 100% CPU | -|[MXS-36](https://mariadb.atlassian.net/browse/MXS-36)|bugzillaId-671: wrong message if SHOW DATABASES privilege is missing| -|[MXS-39](https://mariadb.atlassian.net/browse/MXS-39)|bugzillaId-731:Boolean configuration parameters accept inconsistent parameters| -|[MXS-64](https://mariadb.atlassian.net/browse/MXS-64)|maxkeys and Maxpasswd do not produce informative error output| -|[MXS-25](https://mariadb.atlassian.net/browse/MXS-25)|bugzillaId-656: MySQL Monitor: claims that Master is available after master failure| -|[MXS-82](https://mariadb.atlassian.net/browse/MXS-82)|cmake warns when mariadb is compiled without mysql_release| -|[MXS-69](https://mariadb.atlassian.net/browse/MXS-69)|dbfwfilter should be pessimistic about rule syntax errors| -|[MXS-98](https://mariadb.atlassian.net/browse/MXS-98)|regexfilter log| -|[MXS-28](https://mariadb.atlassian.net/browse/MXS-28)|bugzillaId-433: Logging don't include assert information| -|[MXS-75](https://mariadb.atlassian.net/browse/MXS-75)|"wildcard" rule also blocks COUNT(*)| -|[MXS-118](https://mariadb.atlassian.net/browse/MXS-118)|Two monitors loaded at the same time result into not working installation| -|[MXS-33](https://mariadb.atlassian.net/browse/MXS-33)|bugzillaId-702: CLI: list services command shows negative values for the number of users of a service (Read Service).| -|[MXS-17](https://mariadb.atlassian.net/browse/MXS-17)|bugzillaId-736: Memory leak while doing read/write splitting| -|[MXS-30](https://mariadb.atlassian.net/browse/MXS-30)|bugzillaId-487: Buffer manager should not use pointer arithmetic on void*| -|[MXS-81](https://mariadb.atlassian.net/browse/MXS-81)|cmake fails when init scripts are missing| -|[MXS-127](https://mariadb.atlassian.net/browse/MXS-127)|disable_sescmd_history causes MaxScale to crash under load| +* [MXS-99](https://mariadb.atlassian.net/browse/MXS-99): /etc/init.d/maxscale reload doesn't do anything +* [MXS-83](https://mariadb.atlassian.net/browse/MXS-83): linkage fails when system pcre library is recent +* [MXS-112](https://mariadb.atlassian.net/browse/MXS-112): Disable saving of session commands in the readwritesplit and schemarouter modules +* [MXS-114](https://mariadb.atlassian.net/browse/MXS-114): Disable recovery of disconnected slaves +* [MXS-73](https://mariadb.atlassian.net/browse/MXS-73): MaxScale uses nearly 100% CPU +* [MXS-36](https://mariadb.atlassian.net/browse/MXS-36): bugzillaId-671: wrong message if SHOW DATABASES privilege is missing +* [MXS-39](https://mariadb.atlassian.net/browse/MXS-39): bugzillaId-731:Boolean configuration parameters accept inconsistent parameters +* [MXS-64](https://mariadb.atlassian.net/browse/MXS-64): maxkeys and Maxpasswd do not produce informative error output +* [MXS-25](https://mariadb.atlassian.net/browse/MXS-25): bugzillaId-656: MySQL Monitor: claims that Master is available after master failure +* [MXS-82](https://mariadb.atlassian.net/browse/MXS-82): cmake warns when mariadb is compiled without mysql_release +* [MXS-69](https://mariadb.atlassian.net/browse/MXS-69): dbfwfilter should be pessimistic about rule syntax errors +* [MXS-98](https://mariadb.atlassian.net/browse/MXS-98): regexfilter log +* [MXS-28](https://mariadb.atlassian.net/browse/MXS-28): bugzillaId-433: Logging don't include assert information +* [MXS-75](https://mariadb.atlassian.net/browse/MXS-75): "wildcard" rule also blocks COUNT(*) +* [MXS-118](https://mariadb.atlassian.net/browse/MXS-118): Two monitors loaded at the same time result into not working installation +* [MXS-33](https://mariadb.atlassian.net/browse/MXS-33): bugzillaId-702: CLI: list services command shows negative values for the number of users of a service (Read Service). +* [MXS-17](https://mariadb.atlassian.net/browse/MXS-17): bugzillaId-736: Memory leak while doing read/write splitting +* [MXS-30](https://mariadb.atlassian.net/browse/MXS-30): bugzillaId-487: Buffer manager should not use pointer arithmetic on void* +* [MXS-81](https://mariadb.atlassian.net/browse/MXS-81): cmake fails when init scripts are missing +* [MXS-127](https://mariadb.atlassian.net/browse/MXS-127): disable_sescmd_history causes MaxScale to crash under load + ## Known Issues There are a number bugs and known limitations within this version of MaxScale, the most serious of this are listed below. From f57d5fd26fd146acd7275c2ea2445767211af934 Mon Sep 17 00:00:00 2001 From: Rasmus Johansson Date: Mon, 11 May 2015 10:06:05 +0300 Subject: [PATCH 03/10] Some changes to the first section of the release notes and corrected some typos Some changes to the first section of the release notes and corrected some typos. Also some smaller edits here and there. --- Release-Notes/MaxScale-1.1.1-Release-Notes.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/Release-Notes/MaxScale-1.1.1-Release-Notes.md b/Release-Notes/MaxScale-1.1.1-Release-Notes.md index 47edcb6c3..5904346ac 100644 --- a/Release-Notes/MaxScale-1.1.1-Release-Notes.md +++ b/Release-Notes/MaxScale-1.1.1-Release-Notes.md @@ -2,7 +2,7 @@ ## 1.1 GA -This document details the changes in version 1.1.1 since the release of the 1.1 GA Release of the MaxScale product. +MaxScale 1.1 is the current stable (GA) release of MaxScale. Version 1.1.1 is mainly a bug fix release introducing fixes, but also introduces some improvements to existing functionality. ## New Features @@ -20,7 +20,7 @@ Using the password functionality in MaxScale is now a lot easier. Both programs ## Bug Fixes -Here is a list of bugs fixed since the release of the 1.1 version of MaxScale. The bug IDs are from the **[Mariadb Jira](https://mariadb.atlassian.net/)**. +Here is a list of bugs fixed since the release of the 1.1.0 version of MaxScale. The bug IDs are from the **[MariaDB Jira](https://mariadb.atlassian.net/)**. * [MXS-99](https://mariadb.atlassian.net/browse/MXS-99): /etc/init.d/maxscale reload doesn't do anything * [MXS-83](https://mariadb.atlassian.net/browse/MXS-83): linkage fails when system pcre library is recent @@ -45,18 +45,18 @@ Here is a list of bugs fixed since the release of the 1.1 version of MaxScale. T ## Known Issues -There are a number bugs and known limitations within this version of MaxScale, the most serious of this are listed below. +There are a number bugs and known limitations within this version of MaxScale, the most serious of these are listed below. -* The Read/Write Splitter is a little too strict when it receives errors from slave servers during execution of session commands. This can result in sessions being terminated in situation in which MaxScale could recover without terminating the sessions. +* The Read/Write Splitter is a little too strict when it receives errors from slave servers during execution of session commands. This can result in sessions being terminated in situations from which MaxScale could recover without terminating the sessions. -* MaxScale can not manage authentication that uses wildcard matching in hostnames in the mysql.user table of the backend database. The only wildcards that can be used are in IP address entries. +* MaxScale cannot manage authentication that uses wildcard matching in hostnames in the mysql.user table of the backend database. The only wildcards that can be used are in IP address entries. * When users have different passwords based on the host from which they connect MaxScale is unable to determine which password it should use to connect to the backend database. This results in failed connections and unusable usernames in MaxScale. * Binlog Router Plugin is compatible with MySQL 5.6 Binlog Router Plugin currently does not work for MariaDB 5.5 and MariaDB 10.0 -* LONGBLOG are currently not supported. +* LONGBLOG datatype is currently not supported. * Galera Cluster variables, such as @@wsrep_node_name, are not resolved by the embedded MariaDB parser. @@ -64,7 +64,7 @@ There are a number bugs and known limitations within this version of MaxScale, t ## Packaging -Both RPM and Debian packages are available for MaxScale in addition to the tar based releases previously distributed we now provide +Both RPM and Debian packages are available for MaxScale in addition to the tar based releases. Packages are now provided for: * CentOS/RedHat 5 From 4aa1a9b14081d9e7cc66c90669bb21c86b39eeb4 Mon Sep 17 00:00:00 2001 From: Will Fong Date: Wed, 1 Jul 2015 16:34:57 +0800 Subject: [PATCH 04/10] Updated URL for the SchemaRouter --- Documentation-Contents.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation-Contents.md b/Documentation-Contents.md index dfbef26dc..6753dc929 100644 --- a/Documentation-Contents.md +++ b/Documentation-Contents.md @@ -64,7 +64,7 @@ Here are detailed documents about the filters MaxScale offers. They contain conf ## Routers - - [Simple Schema Sharding Router](routers/schemarouter/SchemaRouter.md) + - [Simple Schema Sharding Router](routers/SchemaRouter.md) ## Design Documents From b345dcda3d2260331ebceeed95dd56adc4f670c6 Mon Sep 17 00:00:00 2001 From: Will Fong Date: Wed, 1 Jul 2015 16:39:57 +0800 Subject: [PATCH 05/10] Missing opening bracket --- routers/SchemaRouter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/routers/SchemaRouter.md b/routers/SchemaRouter.md index d1de66b2b..6fbf4b19a 100644 --- a/routers/SchemaRouter.md +++ b/routers/SchemaRouter.md @@ -15,7 +15,7 @@ In almost all the cases these can be avoided by proper server configuration and Here is an example configuration of the schemarouter router: ``` -Shard Router] +[Shard Router] type=service router=schemarouter servers=server1,server2 From c9c666f77c37026dd496c944e5124bffb7bf28ee Mon Sep 17 00:00:00 2001 From: Will Fong Date: Wed, 1 Jul 2015 16:44:21 +0800 Subject: [PATCH 06/10] Went back one too many levels --- routers/SchemaRouter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/routers/SchemaRouter.md b/routers/SchemaRouter.md index 6fbf4b19a..1d8188889 100644 --- a/routers/SchemaRouter.md +++ b/routers/SchemaRouter.md @@ -64,4 +64,4 @@ The schemarouter router currently has some limitations due to the nature of the ## Examples -[Here](../../Tutorials/Simple-Sharding-Tutorial.md) is a small tutorial on how to set up a sharded database. +[Here](../Tutorials/Simple-Sharding-Tutorial.md) is a small tutorial on how to set up a sharded database. From 1d52bfb66fa9f6e66acd8953aa22957cbd72becd Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Wed, 1 Jul 2015 19:38:45 +0300 Subject: [PATCH 07/10] Updated documentation and set C99 mode as the default. --- monitors/MySQL-Monitor.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/monitors/MySQL-Monitor.md b/monitors/MySQL-Monitor.md index 7228c1b10..6c7e70500 100644 --- a/monitors/MySQL-Monitor.md +++ b/monitors/MySQL-Monitor.md @@ -98,6 +98,14 @@ A list of event names which cause the script to be executed. If this option is n events=master_down,slave_down ``` +### `mysql51_only` + +Enable support for MySQL 5.1 replication monitoring. This is needed if a MySQL server older than 5.5 is used as a slave in replication. + +``` +mysql51_only=true +``` + ## Script events Here is a table of all possible event types and their descriptions. From c60c38794cd73d422c78f7575df898ada423574f Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Tue, 7 Jul 2015 20:14:57 +0300 Subject: [PATCH 08/10] Added error message about MySQL versions lower than 5.5 and monitors without the 'mysql51_replication' enabled. --- monitors/MySQL-Monitor.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/monitors/MySQL-Monitor.md b/monitors/MySQL-Monitor.md index 6c7e70500..e53b7c336 100644 --- a/monitors/MySQL-Monitor.md +++ b/monitors/MySQL-Monitor.md @@ -98,12 +98,12 @@ A list of event names which cause the script to be executed. If this option is n events=master_down,slave_down ``` -### `mysql51_only` +### `mysql51_replication` Enable support for MySQL 5.1 replication monitoring. This is needed if a MySQL server older than 5.5 is used as a slave in replication. ``` -mysql51_only=true +mysql51_replication=true ``` ## Script events From 21a6d63bc0601629ebd36f132dece836e9496700 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Wed, 15 Jul 2015 17:17:47 +0300 Subject: [PATCH 09/10] Fixed broken link. --- About/About-MaxScale.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/About/About-MaxScale.md b/About/About-MaxScale.md index 4477c2907..ef0723914 100644 --- a/About/About-MaxScale.md +++ b/About/About-MaxScale.md @@ -17,7 +17,7 @@ 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). +Information about installing MaxScale, either from a repository or by building from source code, is included in the [MariaDB MaxScale Installation Guide](../Getting-Started/MariaDB-MaxScale-Installation-Guide.md). The same guide also provides basic information on running MaxScale. More detailed information about configuring MaxScale is given in the [Configuration Guide](/Documentation/Getting-Started/Configuration-Guide.md). From 6ee4f5f65537b14e969c07cabbdeda59d5190b76 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Thu, 16 Jul 2015 05:46:22 +0300 Subject: [PATCH 10/10] Fixed type in documentation. --- Getting-Started/MariaDB-MaxScale-Installation-Guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Getting-Started/MariaDB-MaxScale-Installation-Guide.md b/Getting-Started/MariaDB-MaxScale-Installation-Guide.md index 31b713121..bf752b1fd 100644 --- a/Getting-Started/MariaDB-MaxScale-Installation-Guide.md +++ b/Getting-Started/MariaDB-MaxScale-Installation-Guide.md @@ -16,7 +16,7 @@ The simplest way to install MaxScale is to use one of the binary packages that a ![image alt text](images/getting_started.png) -If you want to install only MaxScale, futher down you will find the product specific download pages. Click on the MariaDB MaxScale link and follow the distribution specific instructions. +If you want to install only MaxScale, further down you will find the product specific download pages. Click on the MariaDB MaxScale link and follow the distribution specific instructions. ![image alt text](images/getting_started2.png)