Added the quota exceeded error as retryable error during mergeflush - #482
Open
priyanshu-ctds wants to merge 1 commit into
Open
Added the quota exceeded error as retryable error during mergeflush#482priyanshu-ctds wants to merge 1 commit into
priyanshu-ctds wants to merge 1 commit into
Conversation
Andrey Yegorov (dlg99)
approved these changes
Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #481
When a quota exceeded error occurs during a merge flush, the current code rethrows it immediately without retrying, leaving the failed batch permanently in the internal batches map. This causes all subsequent flush attempts to block indefinitely inside prepareToFlush waiting for the stuck batch to be removed, making the connector silently stop delivering data even after the quota resets.
This PR adds quota exceeded as a retryable error in the merge flush retry logic alongside the existing serialize access and job internal errors. Configuring bigQueryRetry and bigQueryRetryWait such that the total retry window exceeds 24 hours allows the flush to succeed naturally once the quota resets, without any task failure or data loss.