Add binary exponential backoff to _flush_writes#11
Open
blakehawkins wants to merge 1 commit into
Open
Conversation
Flushing changes to a remote document has some probability of error for each batch. For large changesets it becomes unlikely for writes to execute successfully. This commit causes writes to retry on failure using exponential backoff, waiting 1, 2, 4, ... seconds between writes, until success.
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
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.
This PR replaces an old PR that had rotted - I've not tested that this works as I don't have a local project running SheetSync.
Flushing changes to a remote document has some
probability of error for each batch. For large
changesets it becomes unlikely for writes to execute
successfully.
This commit causes writes to retry on failure using
exponential backoff, waiting 1, 2, 4, ... seconds
between writes, until success.