Bug #73292 Slave SQL error 1237 warnings
Submitted: 15 Jul 2014 9:05 Modified: 2 Dec 2014 21:33
Reporter: Valeriy Kravchuk Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Replication Severity:S4 (Feature request)
Version:5.6 OS:Any
Assigned to: CPU Architecture:Any
Tags: replicate-*, slave, warning

[15 Jul 2014 9:05] Valeriy Kravchuk
On the 5.6 slave (of master version 5.5.35) there are many entries warning about Slave SQL: Could not execute Query event. Detailed error: Slave SQL thread ignored the query because of replicate-*-table rules;, Error_code: 1237. On the 5.5 slave there are no warnings.

I know about this change in recent versions (5.6.17+):

"Replication: When a slave was configured with replication filters and --log-warnings=2, every statement which was filtered caused an entry to be written in the error log. For busy servers which generated many statements to be filtered, the result was that the error log could quickly grow to many gigabytes in size. Now a throttle is used for such errors, so that an error message is printed only once in a given interval, saying that this particular error occurred a specific number of times during that interval. (Bug #17986385)"

but can we, please, add some setting/feature to be able to remove all warnings of this kind from the error log with 5.6? Some pre-5.6 compatibility mode maybe, that can do this 9among other things)?

How to repeat:
Set up replication with replicate-*-table filtering on 5.6 slave. Note warnings about skipped statements in the error log. Do something to have only this kind of warnings not appearing in the error log (as it was the case on 5.5 slave). Is  --slave-skip-errors=1237 the only option?

Suggested fix:
Do/add something to be able have only this kind of warnings not appearing in the error log, as it was the case in MySQL 5.5.
[2 Dec 2014 21:33] Sveta Smirnova
Thank you for the reasonable feature request.
[5 Sep 2017 16:19] Steven Hartland
Any news on this guys as having this constantly spam the error log is far from ideal.

This is still present in 5.7.19
[23 Sep 2019 13:55] Dave Rix
This is still a problem as of 5.7.21 in Sept 2019.
It is clouding the error log file, so real errors might get missed.
I do not want to skip this error in the config, as that is not the right thing to do in this situation.
[23 Sep 2019 13:56] Dave Rix
Sorry, I meant 5.7.27