From 3cd07cc5c79ad659b7b7cded8f22658ab023ee36 Mon Sep 17 00:00:00 2001 From: MassimilianoPinto Date: Fri, 20 Mar 2015 09:16:23 +0100 Subject: [PATCH 1/5] Release Notes 1.1. Update Release Notes 1.1. Update --- .../MaxScale-1.1-Release-Notes.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/Documentation/Release-Notes/MaxScale-1.1-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.1-Release-Notes.md index 79a402fd6..824f10005 100644 --- a/Documentation/Release-Notes/MaxScale-1.1-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-1.1-Release-Notes.md @@ -35,12 +35,28 @@ Connection based routing to MySQL NDB clusters # Bug Fixes -A number of bug fixes have been applied between the 1.0.5 GA and this RC release. The table below lists the bugs that have been resolved. The details for each of these may be found in https://mariadb.atlassian.net/projects/MXS +A number of bug fixes have been applied between the 1.0.5 GA and this RC release. The table below lists the bugs that have been resolved. The details for each of these may be found in https://mariadb.atlassian.net/projects/MXS or in the former http://bugs.mariadb.com Bug database + + + + + + + + + + + + + + + + From 31bb4eebe8f08df3fb9528eec1e2d3d77e234b9b Mon Sep 17 00:00:00 2001 From: MassimilianoPinto Date: Fri, 20 Mar 2015 11:06:37 +0100 Subject: [PATCH 2/5] Release Notes 1.0.5 added Release Notes 1.0.5 added --- .../MaxScale-1.0.5-Release-Notes.md | 97 +++++++++++++++++++ 1 file changed, 97 insertions(+) create mode 100644 Documentation/Release-Notes/MaxScale-1.0.5-Release-Notes.md diff --git a/Documentation/Release-Notes/MaxScale-1.0.5-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.0.5-Release-Notes.md new file mode 100644 index 000000000..d63dc8934 --- /dev/null +++ b/Documentation/Release-Notes/MaxScale-1.0.5-Release-Notes.md @@ -0,0 +1,97 @@ +MaxScale Release Notes 1.0.5 GA + +This document details the changes in version 1.0.5 since the release of the 1.0.4 GA of the MaxScale product. + +# New Features +No new features have been introduced since the GA version was released. SuSE Enterprise 11 and 12 packages are now also supplied. + +# Bug Fixes + +A number of bug fixes have been applied between the 1.0.4 initial GA release and this GA release. The table below lists the bugs that have been resolved. The details for each of these may be found in bugs.mariadb.com. + +
ID Summary
MXS-47Session freeze when small tail packet
MXS-5Possible memory leak in readwritesplit router
736Memory leak while doing read/write splitting
733Init-script deletes bin/maxscale
732
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
IDSummary
519LOAD DATA LOCAL INFILE not handled?
714Error log flooded when too many connect errors causes the MaxScale host to be blocked
711Some MySQL Workbench Management actions hang with R/W split router
710make package install files in /etc/init.d
683Check for unsupported version of MariaDB
684Use mysql_config to determine include/lib directory paths and compiler options
689cmake ­DCMAKE_INSTALL_PREFIX has no effect
701set server maint fails on the command line
705Authentication fails when the user connects to a database with the SQL mode including ANSI_QUOTES
507R/W split does not send last_insert_id() to the master
700maxscale ­­version has no output
694RWSplit SELECT @a:=@a+1 as a, test.b from test breaks client session
685SELECT against readconnrouter fails when large volumes of data are returned and the tee filter is used
+ +# Known Issues + +There are a number bugs and known limitations within this version of MaxScale, the most serious of this 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. +● 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. +● 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. + +# Packaging + +Both RPM and Debian packages are available for MaxScale in addition to the tar based releases previously distributed we now provide +● CentOS/RedHat 5 +● CentOS/RedHat 6 +● CentOS/RedHat 7 +● Debian 6 +● Debian 7 +● Ubuntu 12.04 LTS +● Ubuntu 13.10 +● Ubuntu 14.04 LTS +● Fedora 19 +● Fedora 20 +● OpenSuSE 13 +● SuSE Enterprise 11 +● SuSE Enterprise 12 + +# MaxScale Home Default Value + +The installation assumes that the default value for the environment variable MAXSCALE_HOME is set to /usr/local/skysql/maxscale. This is hard coded in the service startup file that is placed in /etc/init.d/maxscale by the installation process. From 85473f842161fb216768c344b7a03f7d14c69f37 Mon Sep 17 00:00:00 2001 From: MassimilianoPinto Date: Fri, 20 Mar 2015 11:09:46 +0100 Subject: [PATCH 3/5] Release Notes 1.1 Update Release Notes 1.1 Update --- .../MaxScale-1.1-Release-Notes.md | 45 ------------------- 1 file changed, 45 deletions(-) diff --git a/Documentation/Release-Notes/MaxScale-1.1-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.1-Release-Notes.md index 824f10005..f542e1b45 100644 --- a/Documentation/Release-Notes/MaxScale-1.1-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-1.1-Release-Notes.md @@ -78,43 +78,18 @@ A number of bug fixes have been applied between the 1.0.5 GA and this RC release 716 $this->getReadConnection()->query('SET @id = 0;'); - - 714 - Error log flooded when too many connect errors causes the MaxScale host to be blocked - - - 711 - Some MySQL Workbench Management actions hang with R/W split router - - - 710 - 'make package' installs files to /etc/init.d - 709 "COPYRIGHT LICENSE README SETUP" files go to /usr/local/skysql/maxscale/ after 'make package' - - - 705 - Authentication fails when the user connects to a database when the SQL mode includes ANSI_QUOTES - 704 "make testall" returns success status (exit code 0) even on failures - - 701 - set server maint fails when called from command line - 698 Using invalid parameter in many maxadmin commands causes MaxScale to fail - - 694 - RWSplit: SELECT @a:=@a+1 as a, test.b FROM test breaks client session - 693 Freeing tee filter's orphaned sessions causes a segfault when embedded server closes @@ -123,22 +98,10 @@ A number of bug fixes have been applied between the 1.0.5 GA and this RC release 690 CPU/architecture is hardcoded into debian/rules - - 689 - "cmake -DCMAKE_INSTALL_PREFIX" has no effect ... - 686 TestService fails because of the modules used in it aren't meant for actual use - - 685 - SELECT against ReadConn fails if a lot of data returned and TEE in use - - - 684 - Use mysql_config to determine include/lib directory paths and compiler options - 677 Race condition in tee filter clientReply @@ -187,14 +150,6 @@ A number of bug fixes have been applied between the 1.0.5 GA and this RC release 579 serviceStartProtocol test crashes - - 519 - LOAD DATA LOCAL INFILE not handled? - - - 507 - rw-split router does not send last_insert_id() to master - 506 Don't write to shm/tmpfs by default without telling and without a way to override it From a1bb4cd3e2331650381cfb5a1a5f45bc05e3fd41 Mon Sep 17 00:00:00 2001 From: MassimilianoPinto Date: Fri, 20 Mar 2015 11:15:15 +0100 Subject: [PATCH 4/5] Release Notes 1.0.5 Update Release Notes 1.0.5 Update --- .../MaxScale-1.0.5-Release-Notes.md | 48 ++++++++++++------- 1 file changed, 32 insertions(+), 16 deletions(-) diff --git a/Documentation/Release-Notes/MaxScale-1.0.5-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.0.5-Release-Notes.md index d63dc8934..4b65fd92f 100644 --- a/Documentation/Release-Notes/MaxScale-1.0.5-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-1.0.5-Release-Notes.md @@ -71,26 +71,42 @@ A number of bug fixes have been applied between the 1.0.4 initial GA release and # Known Issues There are a number bugs and known limitations within this version of MaxScale, the most serious of this 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. -● 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. -● 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. + +* 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. + +* 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. + +* 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. # Packaging Both RPM and Debian packages are available for MaxScale in addition to the tar based releases previously distributed we now provide -● CentOS/RedHat 5 -● CentOS/RedHat 6 -● CentOS/RedHat 7 -● Debian 6 -● Debian 7 -● Ubuntu 12.04 LTS -● Ubuntu 13.10 -● Ubuntu 14.04 LTS -● Fedora 19 -● Fedora 20 -● OpenSuSE 13 -● SuSE Enterprise 11 -● SuSE Enterprise 12 + +* CentOS/RedHat 5 + +* CentOS/RedHat 6 + +* CentOS/RedHat 7 + +* Debian 6 + +* Debian 7 + +* Ubuntu 12.04 LTS + +* Ubuntu 13.10 + +* Ubuntu 14.04 LTS + +* Fedora 19 + +* Fedora 20 + +* OpenSuSE 13 + +* SuSE Enterprise 11 + +* SuSE Enterprise 12 # MaxScale Home Default Value From 25c9dd9b9aac70a195f803f3a931ae0173b00b00 Mon Sep 17 00:00:00 2001 From: MassimilianoPinto Date: Fri, 20 Mar 2015 14:58:07 +0100 Subject: [PATCH 5/5] Fixed Typo in documentation Fixed Typo in documentation --- Documentation/Tutorials/Notification-Service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/Tutorials/Notification-Service.md b/Documentation/Tutorials/Notification-Service.md index fb59bd28d..03edd0378 100644 --- a/Documentation/Tutorials/Notification-Service.md +++ b/Documentation/Tutorials/Notification-Service.md @@ -64,7 +64,7 @@ MaxScale shall send the generated feedback report to a feedback server specified If it’s not possible to send data due to firewall or security settings the report could be generated manually (feedback_user_info is required) via MaxAdmin -MaxScale>show feedback report +MaxScale>show feedbackreport Report could be saved to report.txt file: