Configure the producer flush timeout with the max.poll.interval.ms #382
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
ghost
force-pushed
the
quent/checkpoint-timeout
branch
2 times, most recently
from
924526b to
316b2b3
Compare
ghost
changed the title
ghost
force-pushed
the
quent/checkpoint-timeout
branch
2 times, most recently
from
e729cea to
4672227
Compare
ghost
marked this pull request as ready for review
daniil-quix
requested changes
Jun 12, 2024
ghost
force-pushed
the
quent/checkpoint-timeout
branch
from
4672227 to
8c4278a
Compare
ghost
force-pushed
the
quent/checkpoint-timeout
branch
from
8c4278a to
aac7221
Compare
daniil-quix
approved these changes
Jun 13, 2024
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.
closes #381
Add a configuration option to set a default flush timeout on producers. This ensure the application is not blocked if messages can't be delivered successfully.
consumer.commitdoesn't explicitly support a timeout parameter but rely on a globally configured timeout (probably socket.timeout, TBC).