Export - CSV (All fields)
Export - CSV (Current fields)
MXS-99
/etc/init.d/maxscale reload doesn't do anything
Return value of realloc must not be assigned to provided pointer.
sudden signal 6 abort after running for 2 days
setting log_debug=1 triggers signal 11 crashMXS-136
Check for MaxScale replication heartbeat table existence before creating
For bootstrapping you need to provide the first 4-magic bytes of a binlog file for things to work normally.
maxscale binlog events shown in show services seems to be double-counted for the master connection
New ubuntu repository gives a warning about i386 and causes other problems
/etc/init.d/maxscale configtest
maxadmin output in parsable format
maxkeys and Maxpasswd do not produce informative error output
When no events are read from binlog file, the catchup routine is called only if master server is connected.MXS-242
Add usage scenario for RabbitMQ Filter and Tee filter in Configuration Guide
MaxScale detect non working readwritesplit router
"read-only" transactions to be directed to the slaves by the readwritesplit router
MariaDB10 binlog router compatibilty
MaxScale doesnt support custom logging dir
Concurrency issue while incrementing sessions in qlafilter
Schemarouter authentication for wildcard grants fails without optimize_wildcard
Schemarouter and optimize_wildcard leak memory
disable_sescmd_history causes MaxScale to crash under load
inconsistency in maxkeys/maxpassword output and parameters
Do not run maxscale as root.
Master / Slave Status of Servers not detected for RW split
Remove user name/password from configure-maxscale-repo.rpm and .deb
Binlog Router doesn't handle 16MB larger transmissions
MaxScale repository set up does not work
MariaDB 10 compatilbity with bin log router
Firewall Filter testing
"show sessions" can crash MaxScale
schemarouter hangs if client connects with empty database
core/dbusers.c needs better error messages
"wildcard" rule also blocks COUNT(*)
MaxScale uses nearly 100% CPU
Allow configuring modules dynamically without process restartMXS-67
Mechanism to reload dbfwfilter rules
MaxScale should refuse to load modules if unexpected configuration options are found.
Remove "skysql" from path name in CMAKE file
Corrupted memory or empty value are in Master_host field of SHOW SLAVE STATUS when master connection is broken
Memory leak when creating a new event
Reload config leaks memory
Crash when no arguments given to on_queries clause
Omitting <any|all|strict_all> in users directive causes crash in libdbfwfilter.so(link_rules)
"USE" statement gives unpredictable/unexpected results
"Unknown database" when connecting via schemarouter and providing database name
dbfwfilter on_queries clause appears to be ignored
Wrong rule name in dbfwfilter leads to MaxScale crash