Export - CSV (All fields)
Export - CSV (Current fields)
MXS-1636
M18 Failover presentationMXS-1508
Failover is sometimes triggered on non-simple topologies
Maxscale local user cache corruptMXS-1671
External master support for failover/switchover
C includefile json_api.h includes C++ include file cppdefs.hh
Symbolic link (in config directory) that points to a file should be followed
Allow binding of the backend IP address
[MySQLAuth] Client hostname lookup failed, getnameinfo() returned: 'Name or service not known'.
PamAuth Default Authentication is Different from MariaDB
Mysqlmon switchover does not immediately detect bad new master
Test MaxScale HA Active/Standby & Active/Active Configuration
better backend check and restore process in every test
Test: Stress test, straightforward.
Test: Switchover under harder conditions
Authentication data should be thread specific
Integrate CDC Connector into MaxScale builds
Document MaxScale CDC Connector
Malformed disk image error
Unable to connect to maxscale when dbusers reloads
Authentication can fail if users are loaded at the same time
Excessive logging by MySQLAuth at authentication error (was: MySQLAuth SQLite database can be permanently locked)
Failure to resolve hostname is considered an error
MaxScale crashes if env-variables are used without substitute_variables=1 having been defined
Add possibility to log all SQL statements MaxScale sends to a server.
Module API version is not checked
Too many monitor events are triggered
Fix overflow in master id
Add information about MaxCtrl and Cluster Synchronization to Keepalived document
Remove tutorial on HA with Pacemaker/Corosync
Need remove mutex in sqlite
Update handshake version string
MaxCtrl binary are not included by default in MaxScale package
Security scanner says MaxScale is vulnerable to ancient MySQL vulnerability
Add total and current number of connections to "show threads".
Add failover-ignored-servers to MariaDBMon
CentOS package symbols are stripped
Masking filter accesses wrong command argument.
MariaDBMon yet adding mysqlbackend as the protocol instead of mariadbbackend
Blog post: Pseudo-anonymization for GDPR compliance with MaxScale
After enabling detect_replication_lag, MariaDBMon does not create the maxscale_schema.replication_heartbeat database and table
Add rejoin command to mariadbmon
Benchmark MaxScale 2.2
Adding get_lock and release_lock support
Create a keepalived notify script using which keepalived can turn MaxScale active/passive
Database firewall filter failing with multiple users statements in rules file
Document basic mdbci use-cases
sysbench failed to initialize w/ MaxScale read/write splitter