Skip to content

[improve][pip] PIP-377: Automatic retry for failed acknowledgements #23267

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

lhotari
Copy link
Member

@lhotari lhotari commented Sep 7, 2024

Motivation

In the pip-377.md file

Modifications

In the pip-377.md file

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

@lhotari lhotari added this to the 4.0.0 milestone Sep 7, 2024
@lhotari lhotari self-assigned this Sep 7, 2024
@github-actions github-actions bot added PIP doc Your PR contains doc changes, no matter whether the changes are in markdown or code files. labels Sep 7, 2024
@aloyszhang
Copy link
Contributor

Is there a precise step to reproduce the acknowledgment lost?

@lhotari
Copy link
Member Author

lhotari commented Sep 12, 2024

Is there a precise step to reproduce the acknowledgment lost?

@aloyszhang not yet, there's #22709 and #21958 where it seems that acks get lost.

One possible way that acks could get lost is due to the issue described in #23200 where the number of ack holes exceeds the default limit of 10000. If the the consumer gets reconnected at this time (client connection breaks or due to load balancing event), acks would get lost.
There was a previous attempt to limit the number of ack holes with PIP-299. The problem is that it won't prevent exceeding the limit. The problem described in #23200 is addressed with #23231 (which I'm currently working on).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Your PR contains doc changes, no matter whether the changes are in markdown or code files. PIP ready-to-test release/4.0.5 type/PIP
Development

Successfully merging this pull request may close these issues.

2 participants