Export - CSV (All fields)
Export - CSV (Current fields)
MXS-4700
Binlogrouter treats GTID sequences as 32-bit integers
Don't skip events with LOG_EVENT_IGNORABLE_F flagMXS-1524
Send FDE event to slaves with one buffer instead of two
Binlogrouter: Seconds behind master is always zero
Binlog Router replication breaks without semi-sync set on Primary
Post reboot binlog router entered stuck state
Binlogrouter does not support binlog_checksum=NONE
Binlog router appends -BinlogRouter to master version string again and again ...
Parse error when connecting (through binlog router) from mysql-connector-jMXS-2611
MaxScale binlogrouter does not have a binlog index file
show binlog error msg is incorrect
Binlogrouter breaks if event size exceeds INT_MAX
Mixing quote and double quote in same syntax is not supported
Support Binlog Prefix
maxbinlogcheck to remove transaction from binlog
Resource Leak
Add missing fields to SHOW ALL SLAVES STATUS
Add support for show status like 'slave_received_heartbeats' in binlogserver
Binlog Server setup with MySQL 5.7
Automatically set binlog storage to TREE mode when mariadb10_master_gtid is on
Don't check binlog read position when last event is HEARTBEAT_EVENT
Check Binlog Server setup with MariaDB 10.2
Add support for new variables: @@log_bin, @@max_connections, @@gtid_strict_mode etc
Mark the master server backend as inactive If router is not configured
Binlog server Blog Posts
binlog router does not give proper error when authentication with master fails
Grant information is not described adequately for binlog router
Please recognise some commands seen by the binlog router which trigger error reporting
Maxscale binlog router does not under stand SET NAMES utf8mb4
BLR: Improve disconnection reporting of connections via the MySQL interfaceMXS-132
Add support for mandatory option master-uu-id in MaxScale binlog server
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
Multi-DC conflict resolution
When checksum is in use and there is an error in replication stream master connection the blr_terminate_master_replication has no effect
MaxScale Binlog Server does not allow comma to be in password
If slave is not started after CHANGE MASTER, then Master_log_file is lost when maxscale restarts
Binlogrouter logs an error when a 10.1 slave connects
Better handling of queries in the binlog router
Binlog server: Useful information to provide via maxinfo
Maxscale binlogrouter binlog names are unncessarily length-limited
Relay log write failure
binlogrouter shows MaxScale's binary log coordinates in SHOW SLAVE STATUS
Test semi-sync replication in connector-c
Uncaught exception in binlogrouter
Slave stops on GTID gap caused by binlog filter
More than one primary database in a monitor results in errors in MaxScale GUI
Binlogrouter always opens a new binlog on startup
Binlogrouter cannot write binlog files larger than 4GiB
Binlogrouter runs out of memory on very large transactions