Bug #104765 | Binlog compression - handle impossible to replicate transactions | ||
---|---|---|---|
Submitted: | 30 Aug 2021 9:41 | Modified: | 30 Aug 2021 13:47 |
Reporter: | Sergiu Hlihor | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 8.0.25 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
Tags: | Binlog Compression, Binlog Replication, Transaction_payload |
[30 Aug 2021 9:41]
Sergiu Hlihor
[30 Aug 2021 12:06]
MySQL Verification Team
Hi, > I'm opening this ticket as a reaction to https://bugs.mysql.com/bug.php?id=103672 There is no need to open a new bug as a reaction to another one, you can continue posting to Bug#103672 irrelevant to the status (closed) of that bug. I'm marking this bug as duplicate of Bug#103672 and anything you have to add to it please continue adding directly to Bug#103672. > The public documentation states that transactions may be impossible to replicate, but it does not state clearly how dangerous are the side effects. Feel free to reword the "important note" if you think you can write it better, but it clearly states that it might stop replication, not sure how much clearer one can really be. https://dev.mysql.com/doc/refman/8.0/en/binary-log-transaction-compression.html "... be aware that a large transaction which can be replicated successfully when binary log transaction compression is not in use, might stop replication due to its size when binary log transaction compression is in use. ..." Thanks for your efforts and involvement int this bug report.
[30 Aug 2021 13:47]
Sergiu Hlihor
Please rephrase then from "it will stop" replication to "it will crash replication and rebuilt from backups might be required". Or any other formulation that is truthful about the consequences. "Stop" can easily be interpreted as able to resume without loss of information which is not the case.