Bug #81252 | slave_skip_errors is not dynamic | ||
---|---|---|---|
Submitted: | 30 Apr 2016 8:21 | Modified: | 1 May 2016 14:48 |
Reporter: | Simon Mudd (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.5/5.6/5.7 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | slave_skip_errors |
[30 Apr 2016 8:21]
Simon Mudd
[30 Apr 2016 10:07]
Simon Mudd
So just tried with 5.7.12 but this is the same: root@host [(none)]> set global slave_skip_errors = '1064'; ERROR 1238 (HY000): Variable 'slave_skip_errors' is a read only variable root@host [(none)]> select @@version; +------------+ | @@version | +------------+ | 5.7.12-log | +------------+ 1 row in set (0.00 sec)
[30 Apr 2016 10:09]
MySQL Verification Team
also: http://bugs.mysql.com/bug.php?id=35611
[30 Apr 2016 19:08]
Simon Mudd
Shane, indeed. The problem with all of these options is you don't use them "much". So you tend to forget you need them until the next time you need them which may be some time later. Kris' report in 2008 was a known issue then. I guess if you can afford to restart servers you do not care that much but for anyone running a system 24x7x265 having to restart a server to fix a problem such as this is a major nuisance. On one box it may be a pain but if it's on a large number of slaves at the same time then that's worse. (Think of the server being unavailable and also that it will take some time to warm up again.) I would look forward to seeing this addressed as several other replication issues have been changed in 5.7 to make dynamic configuration possible.
[1 May 2016 14:48]
MySQL Verification Team
Thank you for the bug report.
[17 Oct 2017 12:01]
Daniƫl van Eeden
Also affects MySQL 8.0.3