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

Handle max binlog size exceeded error with smaller batch #165

Merged

Conversation

Saadkhalid913
Copy link

@Saadkhalid913 Saadkhalid913 commented Jul 31, 2024

We add a rescue clause into the chunker to handle only the error raised when binlog size is exceeded
We add a method to reduce stride size in throtter by a given % (default 20, configurable by user)
Backoff will keep happening until it reaches "MIN_STRIDE_SIZE" (set to 1 by now, not configurable at the moment)

@Saadkhalid913 Saadkhalid913 marked this pull request as ready for review August 2, 2024 20:40
@Saadkhalid913 Saadkhalid913 force-pushed the handle-max-binlog-size-exceeded-error-with-smaller-batch branch from 0f33b07 to d6c9a52 Compare August 6, 2024 14:15
@Saadkhalid913
Copy link
Author

Agent successfully ran migration with this version of LHM, and retried with smaller batch size and no errors, logs below
https://schema-migrations-staging.shopifysvc.com/schema-migrations-test-app/staging/main/20240815054742

@Saadkhalid913 Saadkhalid913 merged commit 37152af into master Aug 16, 2024
56 checks passed
@coding-chimp coding-chimp deleted the handle-max-binlog-size-exceeded-error-with-smaller-batch branch February 7, 2025 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants