Bug #80402 Delayed replication configuration does not support sub-second precision

Submitted: 17 Feb 2016 9:44 Modified: 17 Feb 2016 12:09
Reporter: Simon Mudd Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:5.6, 5.6.29 OS:Any
Assigned to: CPU Architecture:Any
Tags: master_delay, replication

[17 Feb 2016 9:44] Simon Mudd
Description:
Replication delay can be induced. this is useful for testing.
See: https://dev.mysql.com/doc/refman/5.6/en/replication-delayed.html

I notice that I am unable to configure this with less than sub-second precision.

This is useful for testing application sensitivity to replication delays.

How to repeat:

-- I have an existing replication setup
myuser@myhost [(none)]> change master to master_delay = 0.4;
Query OK, 0 rows affected (0.03 sec)
myuser@myhost [(none)]> show slave status\G
*************************** 1. row ***************************
...
                    SQL_Delay: 0

Note: this does not show 0.4 and I do not get a warning that the input value has been truncated.

Suggested fix:
Please add a warning if you do not accept the value or truncate it.
Ideally add support for this and try to accept the suggested delay value.
[17 Feb 2016 12:09] MySQL Verification Team
Hello Simon,

Thank you for the report.
Observed with 5.6.29 builds.

Thanks,
Umesh

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.050 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.