hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
MaxScale/Release-Notes/MaxScale-1.0.5-Release-Notes.md
MassimilianoPinto 5527551108 Release Notes 1.0.5 Update 
Release Notes 1.0.5 Update
2015-03-20 11:15:15 +01:00

3.3 KiB
Raw Blame History

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
519 LOAD DATA LOCAL INFILE not handled?
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 install files in /etc/init.d
683 Check for unsupported version of MariaDB
684 Use mysql_config to determine include/lib directory paths and compiler options
689 cmake ­DCMAKE_INSTALL_PREFIX has no effect
701 set server maint fails on the command line
705 Authentication fails when the user connects to a database with the SQL mode including ANSI_QUOTES
507 R/W split does not send last_insert_id() to the master
700 maxscale ­­version has no output
694 RWSplit SELECT @a:=@a+1 as a, test.b from test breaks client session
685 SELECT 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.