Skip to content
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

Track messages that successfully completed the message or error pipeline but failed to get acknowledged due to expired leases #1215

Merged
merged 1 commit into from
Sep 18, 2024

Conversation

danielmarbach
Copy link
Contributor

Backport of #1212 to release-12

…ine but failed to get acknowledged due to expired leases (#1212)

* Tests for the receive strategy

* Make ACK throw a LeaseTimeoutException consistently

* Add Bitfaster caching

* Implement fix

* Cleanup

* Some explanations and better expressiveness

* Cover additional scenario of ACK failing

* Make sure we keep track of to be completed message ids

* Cleanup exception

* Keep track of QueueMessage

* Better log statement

* Add acceptance test for visibility expiry

* Acceptance test to verify expiry

* Fix incorrect log statement

* Tone down immediate retry to debug since immediate retries is a common case that should cause warns

* Exception cosmetics

* Limit concurrency instead

* Properly group dependencies

* Evil whitespace has crept in

* Let the exception bubble up

Co-authored-by: Jayanthi <88632084+soujay@users.noreply.github.com>

* Improve the log statements

---------

Co-authored-by: danielmarbach <danielmarbach@users.noreply.github.com>
Co-authored-by: Jayanthi <88632084+soujay@users.noreply.github.com>
(cherry picked from commit 5872d55)

(cherry picked from commit c32a694)
(cherry picked from commit 78bb31a)
@danielmarbach danielmarbach changed the title Track messages that successfully completed the message or error pipeline but failed to get acknowledged due to expired leases Acknowledge of a message that has failed and exceeded the visibility timeout triggers the critical error and may shut down the endpoint Sep 18, 2024
@soujay soujay changed the title Acknowledge of a message that has failed and exceeded the visibility timeout triggers the critical error and may shut down the endpoint Endpoint shuts down and triggers critical error while acknowledging a message that has failed and exceeded the visibility timeout Sep 18, 2024
@soujay soujay merged commit f1f3e42 into release-12.0 Sep 18, 2024
3 checks passed
@soujay soujay deleted the lease-timeout-fix-r12 branch September 18, 2024 23:11
@soujay soujay changed the title Endpoint shuts down and triggers critical error while acknowledging a message that has failed and exceeded the visibility timeout Track messages that successfully completed the message or error pipeline but failed to get acknowledged due to expired leases Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants