Insufficient max_allowed_packet Size
On This Page
|Applies To||MySQL Source (all variants) with BinLog Pipeline mode.|
|Error Message Text(s)||Increase max_allowed_packet_size or slave_max_allowed_packet on the master!|
- If a packet larger than the
max_allowed_packetsize is received by the MySQL server, it is not written, and the associated Events are stored as Failed Events in the BinLog. When Hevo tries to read these failed Events, it encounters this error.
In the MySQL server, the
max_allowed_packetsets an upper limit on the packet size that can be written to the master database. You must set this system variable to more than the size of the largest packet you anticipate.
To specify the
Navigate to your MySQL Server install directory.
- Open the config file:
my.iniin the case of Windows.
my.cnfin the case of Linux.
Search for the
max_allowed_packetparameter in the file or add it if it does not exist.
Set the required packet size:
For example, to set the value to 1 gigabyte, use one of the following:
max_allowed_packet = 1073741824 max_allowed_packet = 1G
- Restart your MySQL server for the changes to take effect.
Note: The system variable,
slave_max_allowed_packet only determines the largest packet size that a slave can read from a master. Hence, modifying this value does not resolve the error.
Refer to the following table for the list of key updates made to this page:
|Date||Release||Description of Change|