Page MenuHomePhabricator

Manually set "max_allowed_packet" to 1GB for "mysqldump"

Authored by epriestley on Dec 20 2017, 5:50 PM.



We have one production instance with failing database backups since they recently uploaded a 52MB hunk. The production configuration specifies a 64MB "max_allowed_packet" in [mysqld], but this doesn't apply to mysqldump (we'd need to specify it in a separate [mysqldump] section) and mysqldump runs with an effective limit of the default (16MB).

We could change our production config to specify a value in [mysqldump], but just change it unconditionally at execution time since there's no reason for any user to ever want this command to fail because they have too much data.

Test Plan

Dumped locally, will verify production backup goes through cleanly.

Diff Detail

rP Phabricator
Automatic diff as part of commit; lint not applicable.
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

epriestley created this revision.Dec 20 2017, 5:50 PM
epriestley requested review of this revision.Dec 20 2017, 5:51 PM
amckinley accepted this revision.Dec 20 2017, 6:22 PM
This revision is now accepted and ready to land.Dec 20 2017, 6:22 PM
This revision was automatically updated to reflect the committed changes.

I deployed this narrowly to the affected shard and verified the backlog flushed and database dumped properly.