On Monday April 27th, MySQL released a much-anticipated patch release 8.0.20. Along with many bug fixes and improvements, a new property was introduced – binlog-transaction-compression. During our own internal testing we have discovered an incompatibility with our Continuent Tungsten products when this property is enabled.
The newly-released binlog-transaction-compression feature is really interesting because it compresses transaction payloads before being written into the binary logs, which in turn reduces the disk space overhead required for storage. I’m sure many users will be keen to implement this, however at this time the use of binlog-transaction-compression=ON will prevent Replication from functioning correctly.
This applies to the replication functions within Tungsten Clustering and also the standalone Tungsten Replicator. The underlying issue is due to a change in the way compressed transactions are written to the binlogs when this parameter is in use, meaning that the Tungsten Replicator is unable to decode and uncompress the information.
Our engineers have fixed the issue and we expect to include it in our upcoming Tungsten 6.1.4 release later this month; this naturally assuming it passes our rigorous testing currently being conducted.
All other 8.0.20 features do not cause any known issues, and therefore providing this property is left disabled (the default) then Tungsten Clustering and Tungsten Replicator will continue to function correctly.
To learn more about …
- Tungsten Clustering: https://www.continuent.com/solutions/
- Tungsten Replicator: https://www.continuent.com/solutions/tungsten-replicator-all-you-need-to-know/
- MySQL 8.0: https://www.mysql.com/products/enterprise/database/
- Patch release 8.0.20: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-20.html