The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-13. For the latest, interactive version please visit https://mariadb.com/kb/.

HEARTBEAT_LOG_EVENT

This event does not appear in the binary log. It's only sent over the network by a master to a slave server to let it know that the master is still alive, and is only sent when the master has no binlog events to send to slave servers.

This event is never written into the binary log file

  • Timestamp is set to 0
  • Next position is set to last pos
  • Type is set to HEARTBEAT_EVENT (0x1b)

Fields

Example of Transmission (Without CRC32)

T 127.0.0.1:8808 -> 127.0.0.1:57157 [AP]
  23 00 00 04 00 00 00 00    00 1b 67 2b 00 00 22 00    '.........g+..&.
  00 00 ed 01 00 00 20 00    66 6f 6f 2d 62 69 6e 2e    ...... .log-bin.
  31 30 30 30 31 33 39                                  1000139

Network Replication protocol, 5 bytes

  • packet size [3] = 23 00 00 => 00 00 23 => 35 (ok byte + event size)
  • pkt sequence [1] = 04
  • OK indicator [1] = 0 (OK)

Heartbeat event

  • Timestamp [4] = 00 00 00 00 => 0
  • Event Type [1] = 1b => 27
  • Server_id [4] = 67 2b 00 00 => 00 00 2b 67 => 111111
  • Event Size [4] = 22 00 00 00 => 00 00 00 26 => 34 (header + data)
  • Next_pos [4] = ed 01 00 00 => 00 00 01 ed => 493
  • Flags [2] == 20 00 => 00 20 = > 32
Content, string<EOF>
  • log-bin.1000139
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.