Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New diagnostic checking that max_allowed_packet is at least 64M or issue warning, and recommend 128M #1781

Closed
robocoder opened this issue Oct 24, 2010 · 1 comment · Fixed by #13497
Assignees
Labels
Milestone

Comments

@robocoder
Copy link
Contributor

@robocoder robocoder commented Oct 24, 2010

From http://dev.mysql.com/doc/refman/5.1/en/packet-too-large.html

When a MySQL client or the mysqld server receives a packet bigger than max_allowed_packet bytes, it issues a Packet too large error and closes the connection. With some clients, you may also get a Lost connection to MySQL server during query error if the communication packet is too large.

Default server configuration is 1MB. For larger sites, it needs to be increased to MEDIUMBLOB (16MB).

@Emerson

This comment has been minimized.

Copy link

@Emerson Emerson commented Jan 17, 2017

Know this is not high priority, but wanted to chime in and mention that I'm seeing this pretty often.

@mattab mattab changed the title Installation (MySQL): test for max_allowed_packet New diagnostic checking that max_allowed_packet is at least 64M or issue warning, and recommend 128M Aug 25, 2018
@mattab mattab modified the milestones: Backlog (Help wanted), 3.7.0 Aug 25, 2018
@mattab mattab removed the Lower priority label Sep 13, 2018
@tsteur tsteur self-assigned this Sep 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.