Handle BufferErrors by backing off and retrying #673
Merged
Conversation
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
added 2 commits
June 14, 2022 09:41
SirOibaf
approved these changes
Jun 14, 2022
kennethmhc
pushed a commit
to kennethmhc/feature-store-api
that referenced
this pull request
Nov 16, 2022
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.
We are sending messages faster than librdkafka can get them delivered to kafka and the local queue is filling up.
Solution is to back off when this happens and retry the message where it happened. When the bufferError happens we can be sure that the message wasn't sent.
Adding hidden options:
debug_kafkaandkafka_producer_configfor the future for debugging and to optimize producer loop.confluentinc/confluent-kafka-python#341 (comment)
confluentinc/confluent-kafka-dotnet#703