Bug #93034 replication logging - please move to performance_schema
| Submitted: | 31 Oct 2018 18:24 | Modified: | 5 Oct 2022 7:18 |
|---|---|---|---|
| Reporter: | Simon Mudd | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S4 (Feature request) |
| Version: | 8.0.13 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | logging, performance_schema, replication | ||
[31 Oct 2018 18:24]
Simon Mudd
[9 Nov 2018 12:33]
MySQL Verification Team
Hello Simon, Thank you for the feature request! regards, Umesh
[28 Dec 2018 11:15]
Amit Wadkar
I'm also facing this issue in 5.7.17 with MTS(Multi Thread slave)
[26 Mar 2019 12:06]
Simon Mudd
FWIW in 8.0 you can make this go away. Load the dragnet filter and run: SET GLOBAL log_error_services='log_filter_dragnet; log_sink_internal'; SET GLOBAL dragnet.log_error_filter_rules='IF err_code == 10559 then drop.';
[5 Oct 2022 4:50]
Shane Bester
To suppress this spam: [mysqld] log_error_suppression_list='MY-010559'
[5 Oct 2022 7:16]
Simon Mudd
Indeed, but log_error_suppression_list was not available when I opened this bug report. However, the new setting does help filter out such entries.
[5 Oct 2022 7:18]
Simon Mudd
Actually I'm wrong. https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html indicates it was released in 8.0.13. I believe I'd seen this previously and had not seen this new setting when I reported the issue.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.057 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.