Bug #54763 | replication heartbeat is poorly documented | ||
---|---|---|---|
Submitted: | 24 Jun 2010 7:27 | Modified: | 28 Sep 2010 14:14 |
Reporter: | Giuseppe Maxia | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.5,5.1 | OS: | Any |
Assigned to: | Jon Stephens | CPU Architecture: | Any |
Tags: | Docs, heartbeat, replication |
[24 Jun 2010 7:27]
Giuseppe Maxia
[24 Jun 2010 8:51]
Andrei Elkin
5.1 docs indeed refer to the feature. It's done mostly on NDB pages which warns explicitly `The next two options (MASTER_BIND and MASTER_HEARTBEAT_PERIOD) are available in MySQL Cluster NDB 6.3 and later, but are not supported in mainline MySQL 5.1' but at the same time few items penetrated the main docs section Table 5.4. Status Variable p.454 Slave_heartbeat_period, Slave_received_heartbeats. I suggest to search for all references of `heartbeat' to make sure the main docs refer to heartbeat on in the context of the Linux heartbeat.
[28 Sep 2010 14:14]
Jon Stephens
As has been pointed out, this is supported by Cluster and 5.5+ (for which it is documented), and not in mainline 5.1 (which is also documented).
[1 Nov 2010 23:35]
Lenz Grimmer
I did not see this bug report before - I reported BUG#57847 about the same issue.