Bug #94356 | Contribution by Facebook: Fix time granularity in dump thread | ||
---|---|---|---|
Submitted: | 15 Feb 2019 23:13 | Modified: | 17 Apr 2019 11:53 |
Reporter: | FBContrib Admin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 8.0.13 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[15 Feb 2019 23:13]
FBContrib Admin
[15 Feb 2019 23:13]
FBContrib Admin
Fix time granularity in dump thread (*) This code is contributed under the Facebook agreement
Contribution: fb_patch_104.txt (text/plain), 2.88 KiB.
[17 Apr 2019 11:53]
Margaret Fisher
Posted by developer: Changelog entry added for MySQL 8.0.18: The heartbeat interval for a replication slave, which is controlled by the MASTER_HEARTBEAT_PERIOD option of the CHANGE MASTER TO statement, can be specified with a resolution in milliseconds. Previously, the master's binary log dump thread used a granularity of seconds to calculate whether a heartbeat signal should be sent to the slave, causing excessive heartbeat activity in the case of multiple skipped events. To remove this issue, all heartbeat-related calculations by the master and slave are now carried out using a granularity of nanoseconds for precision. Thanks to Facebook for the contribution.
[28 Jun 2019 11:05]
MySQL Verification Team
Bug #81164 marked as duplicate of this one.