Add note about Java sdk 2.x dlq has a default 30s ackTimeout policy #985
Conversation
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
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.
✅ Contribution Checklist
Motivation
Add a 30s ackTimeout when using dlq policy: apache/pulsar#3014
Remove this 30s ackTimeout: apache/pulsar#19486
Relative apache/pulsar#8484 apache/pulsar#19134
When we are using a Java sdk from 2.3.x to 2.10.x to create a subscription with dlq policy, the subscription will create a 30s ackTimeout policy automatically. This strategy may lead to consuming duplicate messages especially in some long time cost tasks.
According to the comment apache/pulsar#8484 (comment), I think maybe we can add a hint about this 30s ackTimeout policy in concepts-messaging.md dlq section.
Modification
Current
Preview
