tag:blogger.com,1999:blog-3577485635097286077.post320896201748225037..comments2018-12-23T02:30:34.158+05:30Comments on Rohit's Blog: MySQL 5.7 Replication: mysqlbinlog tool idempotent mode while applying row events rkalhanshttp://www.blogger.com/profile/01515820270253398672noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-3577485635097286077.post-10905994582513008872015-12-18T23:58:02.817+05:302015-12-18T23:58:02.817+05:30This comment has been removed by a blog administrator.Caterinahttps://www.blogger.com/profile/08144746674065589861noreply@blogger.comtag:blogger.com,1999:blog-3577485635097286077.post-77018012030510617612015-06-25T00:04:54.126+05:302015-06-25T00:04:54.126+05:30This comment has been removed by a blog administrator.Anonymoushttps://www.blogger.com/profile/09754246023303005884noreply@blogger.comtag:blogger.com,1999:blog-3577485635097286077.post-10545872885414180212013-09-20T22:44:24.901+05:302013-09-20T22:44:24.901+05:30Thank you Simon for your valuable feedback. Thank you Simon for your valuable feedback. rkalhanshttps://www.blogger.com/profile/01515820270253398672noreply@blogger.comtag:blogger.com,1999:blog-3577485635097286077.post-59132672390460159242013-09-20T21:31:41.745+05:302013-09-20T21:31:41.745+05:30This option directs the server to ignore the RBR e...This option directs the server to ignore the RBR errors. This means that mysql client will stop if there are other kind of error which ensures that we do not ignore important errors.<br />Just to clarify, this mode is an idempotent mode of mysqlbinlog and not an "ignore all errors" mode. rkalhanshttps://www.blogger.com/profile/01515820270253398672noreply@blogger.comtag:blogger.com,1999:blog-3577485635097286077.post-15495507859175760192013-09-05T07:24:57.322+05:302013-09-05T07:24:57.322+05:30how is this better than just running mysqlbinlog ....how is this better than just running mysqlbinlog ... | mysql -f <br /><br />Justin Swanharthttps://www.blogger.com/profile/08193089637089861226noreply@blogger.comtag:blogger.com,1999:blog-3577485635097286077.post-2802419623521156342013-05-08T03:42:51.046+05:302013-05-08T03:42:51.046+05:30See the following feature requests which are relat...See the following feature requests which are related to this post:<br /><br />http://bugs.mysql.com/bug.php?id=54250<br />http://bugs.mysql.com/bug.php?id=69101<br />http://bugs.mysql.com/bug.php?id=69102<br /><br />That is provide some counters so you can at least see when breakage happens and what type of breakage it was.<br /><br />Also idempotent mode seems to basically "ignore any replication errors that happen and hope for the best". Bug#52450 is a slightly different flavour which tries to allow MySQL to continue for failed statements which if executed will not make the data any worse than it was before. That is in theory they will make the slave more _consistent_ with the master if executed, rather than any other errors which will potentially make the master and slaves' database contents differ. So replication may fail with "auto-repair mode" but if it does you need to manually figure out what the fix is.<br /><br />I would really like to see an auto-repair mode as after an RBR breakage just blindly using idempotent mode is hoping that things will be better and ignoring any problems and I'd rather be a bit more cautious than that.Anonymoushttps://www.blogger.com/profile/13937859381074417278noreply@blogger.com