Page MenuHomePhabricator

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

Authored by epriestley on Dec 20 2017, 5:50 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Mar 1, 7:01 AM
Unknown Object (File)
Feb 7 2024, 10:26 PM
Unknown Object (File)
Feb 3 2024, 5:20 PM
Unknown Object (File)
Feb 3 2024, 5:19 PM
Unknown Object (File)
Feb 3 2024, 5:19 PM
Unknown Object (File)
Jan 24 2024, 11:37 PM
Unknown Object (File)
Jan 22 2024, 8:13 AM
Unknown Object (File)
Jan 21 2024, 8:55 AM
Subscribers
None

Details

Summary

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

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

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.