Merge branch 'release-1.2' into develop
This commit is contained in:
Markus Makela
@ -19,7 +19,8 @@
|
||||
|
||||
## Upgrading MaxScale
|
||||
|
||||
- [Upgrading MaxScale to 1.1.0](Upgrading-To-MaxScale-1.1.0.md)
|
||||
- [Upgrading MaxScale from 1.1.1 to 1.2.0](Upgrading-To-MaxScale-1.2.0.md)
|
||||
- [Upgrading MaxScale from 1.0.5 to 1.1.0](Upgrading-To-MaxScale-1.1.0.md)
|
||||
|
||||
## Reference
|
||||
|
||||
|
||||
@ -22,9 +22,9 @@ After following the instructions on that site you should have a working MariaDB
|
||||
|
||||
The full list of dependencies for the most common distributions is provided in this section. If your system is not listed here, MaxScale building isn't guaranteed to be compatible but might still be successful.
|
||||
|
||||
## RHEL, CentOS and Fedora
|
||||
## RHEL and CentOS
|
||||
|
||||
You will need to install all of the following packages for all versions of RHEL, CentOS and Fedora.
|
||||
You will need to install all of the following packages for all versions of RHEL and CentOS.
|
||||
|
||||
```
|
||||
gcc gcc-c++ ncurses-devel bison glibc-devel cmake libgcc perl make libtool
|
||||
@ -39,7 +39,7 @@ rpm-build
|
||||
|
||||
There are also some version specific packages you need to install.
|
||||
|
||||
#### RHEL 6, 7, CentOS 6, 7, Fedora:
|
||||
#### RHEL 6, 7, CentOS 6, 7:
|
||||
|
||||
```
|
||||
libedit-devel
|
||||
@ -51,17 +51,11 @@ libedit-devel
|
||||
mariadb-devel mariadb-embedded-devel
|
||||
```
|
||||
|
||||
#### RHEL 5, 6, CentOS 5, 6, Fedora 19, 20
|
||||
#### RHEL 5, 6, CentOS 5, 6
|
||||
```
|
||||
MariaDB-devel MariaDB-server
|
||||
```
|
||||
|
||||
#### Fedora 19, 20
|
||||
|
||||
```
|
||||
systemtap-sdt-devel
|
||||
```
|
||||
|
||||
## Ubuntu and Debian
|
||||
|
||||
These packages are required on all versions of Ubuntu and Debian.
|
||||
@ -87,16 +81,13 @@ You will also need some version specific packages.
|
||||
|
||||
#### Earlier versions of Ubuntu or Debian
|
||||
|
||||
For these, you will need to obtain the MariaDB embedded library. It has to be manually extracted from the tarball. But first ascertain what version of glibc is installed. Run the command:
|
||||
For these, you will need to obtain the MariaDB embedded library. It has to be manually extracted from the tarballs at the MariaDB site. But first ascertain what version of glibc is installed. Run the command:
|
||||
|
||||
```
|
||||
dpkg -l | grep libc6
|
||||
```
|
||||
|
||||
which will show the version number. If the version is less than 2.14 you should obtain the library from:
|
||||
[https://downloads.mariadb.org/interstitial/mariadb-5.5.41/bintar-linux-x86_64/mariadb-5.5.41-linux-x86_64.tar.gz](https://downloads.mariadb.org/interstitial/mariadb-5.5.41/bintar-linux-x86_64/mariadb-5.5.41-linux-x86_64.tar.gz).
|
||||
Otherwise, from:
|
||||
[https://downloads.mariadb.org/interstitial/mariadb-5.5.41/bintar-linux-glibc_214-x86_64/mariadb-5.5.41-linux-glibc_214-x86_64.tar.gz](https://downloads.mariadb.org/interstitial/mariadb-5.5.41/bintar-linux-glibc_214-x86_64/mariadb-5.5.41-linux-glibc_214-x86_64.tar.gz)
|
||||
which will show the version number. For versions older than 2.14 you should obtain the library which supports GLIBC versions older than 2.14 and for newer versions, the library which supports newer GLIBC versions should be used.
|
||||
|
||||
The suggested location for extracting the tarball is `/usr` so the operation can be done by the following commands:
|
||||
|
||||
@ -107,22 +98,6 @@ The suggested location for extracting the tarball is `/usr` so the operation can
|
||||
|
||||
where /path/to/mariadb.library.tar.gz is replaced by the actual path and name of the downloaded tarball.
|
||||
|
||||
## OpenSUSE
|
||||
|
||||
At the time this guide was written, the MariaDB development packages for OpenSUSE were broken and the build failed.
|
||||
|
||||
The packages required are:
|
||||
|
||||
```
|
||||
gcc gcc-c++ ncurses-devel bison glibc-devel cmake libgcc_s1 perl
|
||||
make libtool libopenssl-devel libaio libaio-devel
|
||||
libedit-devel librabbitmq-devel
|
||||
MariaDB-devel MariaDB-client MariaDB-server
|
||||
```
|
||||
|
||||
If zypper ask which MariaDB client should be installed `MariaDB-client` or `mariadb-client`
|
||||
please select `MariaDB-client`. This is the package provided by the MariaDB repository.
|
||||
|
||||
# Obtaining the MaxScale Source Code
|
||||
|
||||
Now clone the GitHub project to your machine either via the web interface, your favorite graphical interface or the git command line
|
||||
@ -152,16 +127,15 @@ wipe the build directory clean without the danger of deleting important files wh
|
||||
something goes wrong. Building 'out-of-source' also allows you to have multiple
|
||||
configurations of MaxScale at the same time.
|
||||
|
||||
The default values that CMake uses can be found in the 'macros.cmake' file.
|
||||
If you wish to change these, edit the 'macros.cmake' file or define the
|
||||
variables manually at configuration time.
|
||||
The default values that MaxScale uses for CMake can be found in the 'macros.cmake' file under the `cmake` folder.
|
||||
If you wish to change these, edit the 'macros.cmake' file or define the variables manually at configuration time.
|
||||
|
||||
To display all CMake variables with their descriptions:
|
||||
|
||||
```
|
||||
cmake .. -LH
|
||||
```
|
||||
This is a useful command if you have your libraries installed in non-standard locations.
|
||||
This is a useful command if you have your libraries installed in non-standard locations and need to provide them manually.
|
||||
|
||||
When you are ready to run cmake, provide the following command:
|
||||
|
||||
@ -241,7 +215,7 @@ $ make install
|
||||
|
||||
This will result in an installation being created which is identical to that which would be achieved by installing the binary package.
|
||||
|
||||
By default, MaxScale installs to `/usr/local/mariadb-maxscale` and places init.d scripts and ldconfig files into their folders. Change the `CMAKE_INSTALL_PREFIX` variable to your desired installation directory and set `WITH_SCRIPTS=N` to prevent the init.d script and ldconfig file installation.
|
||||
When building from source, MaxScale installs to `/usr/local/` and places init.d scripts and ldconfig files into their folders. Change the `CMAKE_INSTALL_PREFIX` variable to your desired installation directory and set `WITH_SCRIPTS=N` to prevent the init.d script and ldconfig file installation.
|
||||
|
||||
Other useful targets for Make are `documentation`, which generates the Doxygen documentation, and `uninstall` which uninstall MaxScale binaries after an install.
|
||||
|
||||
|
||||
@ -27,31 +27,73 @@ A quick list of changes in installation directories and file names:
|
||||
### Client side SSL encryption
|
||||
MaxScale now supports SSL/TLS encrypted connections to MaxScale.
|
||||
|
||||
### Monitor scripts
|
||||
State changes in backend servers can now trigger the execution of a custom script. With this you can easily customize MaxScale's behavior.
|
||||
### Launchable scripts
|
||||
Now you can configure MaxScale monitor module to automatically launch a script when it detects change in the state of a backend server. The script can be any customer script defined by you to take diagnostic or reporting action. With this you can easily customize MaxScale's behavior.
|
||||
|
||||
### Lsyncd configuration guide
|
||||
A new tutorial has beed added which helps you keep MaxScale's configuration files in sync across multiple hosts. This allows for easier HA setups with MaxScale and guarantees up-to-date configuration files on all nodes. The tutorial can be found [here](../Reference/MaxScale-HA-with-lsyncd.md).
|
||||
|
||||
## Bug fixes
|
||||
|
||||
Here is a list of bugs fixed since the release of MaxScale 1.1.1.
|
||||
|
||||
| Key | Summary |
|
||||
| --- | -------- |
|
||||
| [MXS-24](https://mariadb.atlassian.net/browse/MXS-24) | bugzillaId-604: Module load path documentation issues ... |
|
||||
| [MXS-40](https://mariadb.atlassian.net/browse/MXS-40) | Display logged in users |
|
||||
| [MXS-113](https://mariadb.atlassian.net/browse/MXS-113) | MaxScale seems to fail if built against MariaDB 10.0 libraries |
|
||||
| [MXS-116](https://mariadb.atlassian.net/browse/MXS-116) | Do not run maxscale as root. |
|
||||
| [MXS-125](https://mariadb.atlassian.net/browse/MXS-125) | inconsistency in maxkeys/maxpassword output and parameters |
|
||||
| [MXS-136](https://mariadb.atlassian.net/browse/MXS-136) | Check for MaxScale replication heartbeat table existence before creating |
|
||||
| [MXS-137](https://mariadb.atlassian.net/browse/MXS-137) | cannot get sql for queries with length >= 0x80 |
|
||||
| [MXS-139](https://mariadb.atlassian.net/browse/MXS-139) | Schemarouter authentication for wildcard grants fails without optimize_wildcard |
|
||||
| [MXS-140](https://mariadb.atlassian.net/browse/MXS-140) | strip_db_esc does not work without auth_all_servers |
|
||||
| [MXS-162](https://mariadb.atlassian.net/browse/MXS-162) | Fix Incorrect info in Configuration Guide |
|
||||
| [MXS-163](https://mariadb.atlassian.net/browse/MXS-163) | Reload config leaks memory |
|
||||
| [MXS-165](https://mariadb.atlassian.net/browse/MXS-165) | Concurrency issue while incrementing sessions in qlafilter |
|
||||
| [MXS-166](https://mariadb.atlassian.net/browse/MXS-166) | Memory leak when creating a new event |
|
||||
| [MXS-171](https://mariadb.atlassian.net/browse/MXS-171) | Allow reads on master for readwritesplit |
|
||||
| [MXS-176](https://mariadb.atlassian.net/browse/MXS-176) | Missing dependencies in documentation |
|
||||
| [MXS-181](https://mariadb.atlassian.net/browse/MXS-181) | Poor performance on TCP connection due to Nagle's algoritm |
|
||||
| [MXS-212](https://mariadb.atlassian.net/browse/MXS-212) | Stopped services accept connections |
|
||||
| [MXS-225](https://mariadb.atlassian.net/browse/MXS-225) | RPM Debug build packages have no debugging symbols |
|
||||
| [MXS-227](https://mariadb.atlassian.net/browse/MXS-227) | Memory leak in Galera Monitor |
|
||||
* [MXS-24](https://mariadb.atlassian.net/browse/MXS-24): bugzillaId-604: Module load path documentation issues ...
|
||||
* [MXS-40](https://mariadb.atlassian.net/browse/MXS-40): Display logged in users
|
||||
* [MXS-113](https://mariadb.atlassian.net/browse/MXS-113): MaxScale seems to fail if built against MariaDB 10.0 libraries
|
||||
* [MXS-116](https://mariadb.atlassian.net/browse/MXS-116): Do not run maxscale as root.
|
||||
* [MXS-117](https://mariadb.atlassian.net/browse/MXS-117): Allow configuration of the log file directory
|
||||
* [MXS-125](https://mariadb.atlassian.net/browse/MXS-125): inconsistency in maxkeys/maxpassword output and parameters
|
||||
* [MXS-128](https://mariadb.atlassian.net/browse/MXS-128): cyclic dependency utils -> log_manager -> utils
|
||||
* [MXS-136](https://mariadb.atlassian.net/browse/MXS-136): Check for MaxScale replication heartbeat table existence before creating
|
||||
* [MXS-137](https://mariadb.atlassian.net/browse/MXS-137): cannot get sql for queries with length >= 0x80
|
||||
* [MXS-139](https://mariadb.atlassian.net/browse/MXS-139): Schemarouter authentication for wildcard grants fails without optimize_wildcard
|
||||
* [MXS-140](https://mariadb.atlassian.net/browse/MXS-140): strip_db_esc does not work without auth_all_servers
|
||||
* [MXS-162](https://mariadb.atlassian.net/browse/MXS-162): Fix Incorrect info in Configuration Guide
|
||||
* [MXS-165](https://mariadb.atlassian.net/browse/MXS-165): Concurrency issue while incrementing sessions in qlafilter
|
||||
* [MXS-166](https://mariadb.atlassian.net/browse/MXS-166): Memory leak when creating a new event
|
||||
* [MXS-171](https://mariadb.atlassian.net/browse/MXS-171): Allow reads on master for readwritesplit
|
||||
* [MXS-176](https://mariadb.atlassian.net/browse/MXS-176): Missing dependencies in documentation
|
||||
* [MXS-179](https://mariadb.atlassian.net/browse/MXS-179): Keep configuration changes in synch across MaxScale Mate Nodes
|
||||
* [MXS-180](https://mariadb.atlassian.net/browse/MXS-180): MariaDB10 binlog router compatibilty
|
||||
* [MXS-181](https://mariadb.atlassian.net/browse/MXS-181): Poor performance on TCP connection due to Nagle's algoritm
|
||||
* [MXS-182](https://mariadb.atlassian.net/browse/MXS-182): SHOW SLAVE STATUS and maxadmin "show services" for binlog router needs updated when used with MariaDB 10 Master
|
||||
* [MXS-212](https://mariadb.atlassian.net/browse/MXS-212): Stopped services accept connections
|
||||
* [MXS-225](https://mariadb.atlassian.net/browse/MXS-225): RPM Debug build packages have no debugging symbols
|
||||
* [MXS-227](https://mariadb.atlassian.net/browse/MXS-227): Memory leak in Galera Monitor
|
||||
* [MXS-244](https://mariadb.atlassian.net/browse/MXS-244): Memory leak when using prepared statements without arguments
|
||||
|
||||
## Known Issues and Limitations
|
||||
|
||||
There are a number bugs and known limitations within this version of MaxScale, the most serious of this are listed below.
|
||||
|
||||
* 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.
|
||||
|
||||
* LONGBLOB are currently not supported.
|
||||
|
||||
* Galera Cluster variables, such as @@wsrep_node_name, are not resolved by the embedded MariaDB parser.
|
||||
|
||||
* The Database Firewall filter does not support multi-statements. Using them will result in an error being sent to the client.
|
||||
|
||||
## 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 14.04 LTS
|
||||
|
||||
* SuSE Linux Enterprise 11
|
||||
|
||||
* SuSE Linux Enterprise 12
|
||||
|
||||
24
Documentation/Upgrading-To-MaxScale-1.2.0.md
Normal file
24
Documentation/Upgrading-To-MaxScale-1.2.0.md
Normal file
@ -0,0 +1,24 @@
|
||||
# Upgrading MaxScale from 1.1 to 1.2
|
||||
|
||||
This document describes upgrading MaxScale from version 1.1.1 to 1.2 and the major differences in the new version compared to the old version. The major changes can be found in the `Changelog.txt` file in the installation directory and the official release notes in the `ReleaseNotes.txt` file.
|
||||
|
||||
## Installation
|
||||
|
||||
Before starting the upgrade, we recommend you back up your configuration, log and binary log files in `/usr/local/mariadb-maxscale/`.
|
||||
|
||||
Upgrading MaxScale will copy the `MaxScale.cnf` file in `/usr/local/mariadb-maxscale/etc/` to `/etc/` and renamed to `maxscale.cnf`. Binary log files are not automatically copied and should be manually moved from `/usr/local/mariadb-maxscale` to `/var/lib/maxscale/`.
|
||||
|
||||
## File location changes
|
||||
|
||||
MaxScale 1.2 follows the [FHS-standard](http://www.pathname.com/fhs/) and installs to `/usr/` and `/var/` subfolders. Here are the major changes and file locations.
|
||||
|
||||
* Configuration files are located in `/etc/` and use lowercase letters: `/etc/maxscale.cnf`
|
||||
* Binary files are in `/usr/bin/`
|
||||
* Libraries and modules are in `/usr/lib64/maxscale/`. If you are using custom modules, please make sure they are in this directory before starting MaxScale.
|
||||
* Log files are in the `var/log/maxscale/` folder
|
||||
* MaxScale's PID file is located in `/var/run/maxscale/maxscale.pid`
|
||||
* Data files and other persistent files are in `/var/lib/maxscale/`
|
||||
|
||||
## Running MaxScale without root permissions
|
||||
|
||||
MaxScale can run as a non-root user with the 1.2 version. RPM and DEB packages install the `maxscale` user and `maxscale` group which are used by the init scripts and systemd configuration files. If you are installing from a binary tarball, you can run the `postinst` script included in it to manually create these groups.
|
||||
@ -1457,7 +1457,7 @@ int skygw_log_write(
|
||||
* Write log string to buffer and add to file write list.
|
||||
*/
|
||||
|
||||
for (i = LOGFILE_FIRST; i<LOGFILE_LAST; i <<=1)
|
||||
for (i = LOGFILE_FIRST; i<=LOGFILE_LAST; i <<=1)
|
||||
{
|
||||
/**
|
||||
* If particular log is disabled in general and it is not enabled for
|
||||
|
||||
@ -4011,7 +4011,7 @@ static bool execute_sescmd_in_backend(
|
||||
bool succp;
|
||||
int rc = 0;
|
||||
sescmd_cursor_t* scur;
|
||||
|
||||
GWBUF* buf;
|
||||
if(backend_ref == NULL)
|
||||
{
|
||||
skygw_log_write(LE,"Error: NULL parameter passed to execute_sescmd_in_backend. (%s:%d)",__FILE__,__LINE__);
|
||||
@ -4048,27 +4048,9 @@ static bool execute_sescmd_in_backend(
|
||||
/** Cursor is left active when function returns. */
|
||||
sescmd_cursor_set_active(scur, true);
|
||||
}
|
||||
#if defined(SS_DEBUG)
|
||||
LOGIF(LT, tracelog_routed_query(scur->scmd_cur_rses,
|
||||
"execute_sescmd_in_backend",
|
||||
backend_ref,
|
||||
sescmd_cursor_clone_querybuf(scur)));
|
||||
|
||||
{
|
||||
GWBUF* tmpbuf = sescmd_cursor_clone_querybuf(scur);
|
||||
uint8_t* ptr = GWBUF_DATA(tmpbuf);
|
||||
unsigned char cmd = MYSQL_GET_COMMAND(ptr);
|
||||
buf = sescmd_cursor_clone_querybuf(scur);
|
||||
|
||||
LOGIF(LD, (skygw_log_write(
|
||||
LOGFILE_DEBUG,
|
||||
"%lu [execute_sescmd_in_backend] Just before write, fd "
|
||||
"%d : cmd %s.",
|
||||
pthread_self(),
|
||||
dcb->fd,
|
||||
STRPACKETTYPE(cmd))));
|
||||
gwbuf_free(tmpbuf);
|
||||
}
|
||||
#endif /*< SS_DEBUG */
|
||||
switch (scur->scmd_cur_cmd->my_sescmd_packet_type) {
|
||||
case MYSQL_COM_CHANGE_USER:
|
||||
/** This makes it possible to handle replies correctly */
|
||||
@ -4077,7 +4059,7 @@ static bool execute_sescmd_in_backend(
|
||||
dcb,
|
||||
NULL,
|
||||
dcb->session,
|
||||
sescmd_cursor_clone_querybuf(scur));
|
||||
buf);
|
||||
break;
|
||||
|
||||
case MYSQL_COM_INIT_DB:
|
||||
@ -4103,10 +4085,11 @@ static bool execute_sescmd_in_backend(
|
||||
* Mark session command buffer, it triggers writing
|
||||
* MySQL command to protocol
|
||||
*/
|
||||
|
||||
gwbuf_set_type(scur->scmd_cur_cmd->my_sescmd_buf, GWBUF_TYPE_SESCMD);
|
||||
rc = dcb->func.write(
|
||||
dcb,
|
||||
sescmd_cursor_clone_querybuf(scur));
|
||||
buf);
|
||||
break;
|
||||
}
|
||||
|
||||
@ -4116,6 +4099,7 @@ static bool execute_sescmd_in_backend(
|
||||
}
|
||||
else
|
||||
{
|
||||
while((buf = GWBUF_CONSUME_ALL(buf)) != NULL);
|
||||
succp = false;
|
||||
}
|
||||
return_succp:
|
||||
|
||||
Reference in New Issue
Block a user