Bug #45441 MySQL should have a datetime for the last slave heartbeat

• Submitted: 11 Jun 2009 6:32
• Modified: 14 Dec 2010 6:18
• Reporter: Andrew Hutchings
• Status: Closed
• Category: MySQL Server: Replication
• Severity: S4 (Feature request)
• Version: 6.0.11-alpha
• OS: Any
• Assigned to: Andrew Hutchings
• CPU Architecture: Any
• Tags: Contribution

[11 Jun 2009 6:32] Andrew Hutchings

Description:
The new replication heartbeat feature has a status variable which shows the count of the heartbeats, but not when the last heartbeat was received which could be useful for some monitoring applications.

How to repeat:
SHOW STATUS like '%heartbeat%';

Suggested fix:
The attached patch adds the variable 'Slave_last_heartbeat' which records the datetime of when the last heartbeat was received.

[11 Jun 2009 6:33] Andrew Hutchings

Patch to implement this feature

Attachment: mysql-6.0.11-alpha-last-heartbeat.patch (application/octet-stream, text), 3.08 KiB.

[17 Jun 2009 14:54] Bugs System

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/76472

2779 Andrew Hutchings	2009-06-17
      Bug #45441 MySQL should have a datetime for the last slave heartbeat
            
      Adds the status variable 'Slave_last_heartbeat' which records the datetime of when the last heartbeat was received.

[27 Oct 2009 7:11] Andrew Hutchings

I suggest this is backported to 5.4.4 if possible since the heartbeat mechanism seems to be in there.

[6 Dec 2009 21:45] Bugs System

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/93004

2923 Andrew Hutchings	2009-12-06
      Bug #45441 MySQL should have a datetime for the last slave heartbeat
                  
      Adds the status variable 'Slave_last_heartbeat' which records the datetime of when
      the last heartbeat was received.
      
      Port to MySQL 5.5 and remove un-needed mutex lock.

[29 Nov 2010 18:36] Bugs System

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/125411

3395 Luis Soares	2010-11-29 [merge]
      BUG#45441: MySQL should have a datetime for the last slave heartbeat
      
      Merging Andrew's patch to latest mysql-trunk-bugfixing. Had to
      do a minor change in show_slave_last_heartbeat, to remove
      pthread_mutex_(un)lock and replace it with mysql_mutex_(un)lock.

[29 Nov 2010 19:02] Luis Soares

Queued in mysql-trunk-bugfixing.

[5 Dec 2010 12:44] Bugs System

Pushed into mysql-trunk 5.6.1 (revid:[e-mail]-20101205122447-6x94l4fmslpbttxj) (version source revid:[e-mail]-20101205122447-6x94l4fmslpbttxj) (merge vers: 5.6.1) (pib:23)

[14 Dec 2010 6:18] Jon Stephens

Documented feature addition in the 5.6.1 changelog as follows:

        Added the Slave_last_heartbeat status variable, which shows 
        when a replication slave last received a heartbeat signal. The 
        value is displayed using TIMESTAMP format.

Also updated summary tables with info about new variable.

Closed.