COM_BINLOG_DUMP

This is a command the replica sends to the master after COM_REGISTER_SLAVE.

The master server sends the binlog events from the requested file and position, or if GTID registration is in use, from the GTID value set in the earlier registration phase.

The payload is:

• uint<1> command (COM_BINLOG_DUMP = 0x12).

• uint<4> The requested binlog position.

• Flags.

• Slave server_id.

• The requested binlog file name.

Note

• Flags, usually set to 0. It can be set to BINLOG_SEND_ANNOTATE_ROWS_EVENT (0x02) if the replica server wants to receive the MariaDB 10 events. It can also be set to BINLOG_DUMP_NON_BLOCK (1), in the case the replica is receiving an EOF packet after the last event sent by the master.

• Requested binlog position can be 4 when registering to master server for the very first time or when requesting events from a particular binlog file from the beginning of it.

When replication resumes or it is restarted (STOP REPLICA; START REPLICA), the replica server always sends the latest binlog file name and position, even if GTID registration is in place.

Example of COM_BINLOG_DUMP

After 4 bytes network protocol header we can see:

• Command [1] = 12.

• Requested binlog position [4] = 34 06 00 00 => 00 00 06 34 = 1588.

• Flags [2] = 02 00 => 2 = BINLOG_SEND_ANNOTATE_ROWS_EVENT.

• Binlog file[n] = mysql-bin.000034.

_{This page is licensed: CC BY-SA / Gnu FDL}