Comments on: Replication Issues and Binlog Compressor https://www.percona.com/blog/replication-issues-and-binlog-compressor/ Wed, 05 Apr 2023 13:42:26 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: Denis Subbota https://www.percona.com/blog/replication-issues-and-binlog-compressor/#comment-10974045 Wed, 05 Apr 2023 13:42:26 +0000 https://www.percona.com/blog/?p=86350#comment-10974045 Hello Kenny,
Thanks for checking blog.

Binlog compression, it’s when you are using script which is compressing for you binlary logs based on your time policy.
It might be a simple cron task in bundle find + gzip or you can create a script for same :
Example:
## Binlog compression for files older than day
15,45 * * * * root find /path/to/binlog -maxdepth 1 -type f -mtime +1 -name “mysql-binlog.??????” -exec gzip {} \;

Thanks for sharing about built-in binlog transaction compression. This is something that needs to be checked first. I am curious if enabled binlog trx compression will be causing CPU overwhelming for replicas.

Regards,
Denis Subbota.
Managed Services, Percona.

]]>
By: Kenny Gryp https://www.percona.com/blog/replication-issues-and-binlog-compressor/#comment-10974032 Tue, 28 Mar 2023 21:27:41 +0000 https://www.percona.com/blog/?p=86350#comment-10974032 What binlog compression is talked about here? Is this about manually compressing binlog files using gzip? Then that’s normal that things don’t work as expected.

Use binlog transaction compression instead, then these problems do not happen (https://dev.mysql.com/doc/refman/8.0/en/binary-log-transaction-compression.html). This has been released 3 years ago.

]]>