-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Async producer retries for failed messages #331
Merged
Merged
Changes from all commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
b82f94f
Retries for async batching
vshlapakov 81d8688
Fixed base producer imports
vshlapakov 4b8288a
Producer _send_upstream fixes, added tests for retries
vshlapakov a9324f3
Fixed compatible issues with tests
vshlapakov 566e408
Fix: check failed reqs to retry only for positive limit
vshlapakov b0a0459
Returned default behaviour with no retries
vshlapakov 5e8dc6d
Fixed tests and other issues after rebase
vshlapakov 09c1c8b
Improved retry logic
vshlapakov 0e0f794
Arg fixes for base/keyed producers
vshlapakov b311145
Clean and simplify retry logic
vshlapakov c165f17
Disable retry on timeouts by default (old behaviour)
vshlapakov cf36308
add producer send batch queue overfilled test
f41e5f3
async queue: refactored code; add one more test
ediskandarov 948e046
Fix small issues with names/tests
vshlapakov 7da48f6
Simplification of retry logic
vshlapakov 5119bb6
Fix names for async retries opts, add timeout for put
vshlapakov 91af27c
Fix async producer queue put arguments
vshlapakov 9eed169
Change backoff message log level
vshlapakov 4c682f3
Increase producer test timeout
vshlapakov a3fb322
Improve async producer code: logic and style fixes
vshlapakov 4474a50
Async producer: py2.6 backward compatibility fix
vshlapakov 7d6f3f5
Check response.error for async producer
vshlapakov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we'll need to have a way to let the user know which messages were successfully added to the queue, and which were not (because we loop
for m in msg
it is possible that the first n messages are added, but msg n+1 raises the exception.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! My proposal is tracking index
n
and returnmsg[n+1:]
asfailed_msgs
property's value ofAsyncProducerQueueFull
exception.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that would work