Bug #35611 please make all slave replication options dynamic
Submitted: 27 Mar 2008 14:38 Modified: 28 Mar 2008 13:57
Reporter: Kristian Koehntopp Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Replication Severity:S4 (Feature request)
Version:5.0, 5.1, 5.5,5.6,5.7 OS:Any
Assigned to: Luis Soares CPU Architecture:Any
Triage: Triaged: D5 (Feature request)

[27 Mar 2008 14:38] Kristian Koehntopp
To work around http://bugs.mysql.com/bug.php?id=35608 I wanted to ignore the resulting errors 1048. This is not possible without a server restart, because slave_skip_errors is not a dynamic variable.

How to repeat:
mysql> set global slave_skip_errors='1048';
ERROR 1193 (HY000): Unknown system variable 'slave_skip_errors'

Suggested fix:
Make it dynamic!
[28 Mar 2008 13:57] Susanne Ebrecht
Verified as described by using 5.1-bk-tree.

mysql> select version();
| version()       |
| 5.1.24-rc-debug | 

mysql> show global variables like 'slave_skip_errors';
| Variable_name     | Value |
| slave_skip_errors | OFF   | 
1 row in set (0.00 sec)

mysql> set global slave_skip_errors='1048';
ERROR 1193 (HY000): Unknown system variable 'slave_skip_errors'
[17 May 2010 6:53] Shane Bester
this feature request applies to all replication options not dynamically settable:


for the simple changes, we don't like to have to use techniques like:
http://mituzas.lt/2009/07/30/evil-replication-management/ as they maybe unsupported.
[19 Oct 2010 9:52] Shane Bester
related: bug #57560
[13 Mar 2012 10:21] Shane Bester
We also need relay_log_space_limit to be made dynamic..
[18 Jul 2012 20:32] Vasiliy Boulytchev
Folks, its 2012, same issue persists.  Any reason why not make this variable dynamic?
[10 Oct 2014 8:27] Daniƫl van Eeden
It looks like this is (partly?) fixed in 5.7.3+

"In MySQL 5.7.3 and later, CHANGE REPLICATION FILTER sets one or more replication filtering rules on the slave in the same way as starting the slave mysqld with replication filtering options such as --replicate-do-db or --replicate-wild-ignore-table. Unlike the case with the server options, this statement does not require restarting the server to take effect, only that the slave SQL thread be stopped using STOP SLAVE SQL_THREAD first (and restarted with START SLAVE SQL_THREAD afterwards)."
[10 Feb 2017 21:31] Miguel Solorzano
https://bugs.mysql.com/bug.php?id=84955 marked as duplicate of this one.
[9 Feb 2018 14:23] Sven Sandberg
Posted by developer:
See also WL#10333: Session profiles.