Pulsar support for retry and DLQ #1333
Open
+1,336
−32
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
3.11 update
Author
|
Hey @jeremydmiller |
added 8 commits
March 27, 2025 13:49
…s sync with Pulsar RECONSUMETIMES header
…red endpoints, added first test for it
…on waiting for DLQ envelope
… MoveToRetryLetterQueueAsync from the lifecycle
Member
|
@punxrok Couple things:
|
added 6 commits
April 14, 2025 11:56
…be deleted in next commit) with ISupportNativeScheduling for Pulsar's native retry letter functionality.
…m the previously modified code
…viously modified code
…viously modified code - removed DotPulsar.Extensions.Resiliency (retry and delay message functionality was not working properly) and created "in-house" retry and DLQ functionalities
Author
|
@jeremydmiller, I have tried to address your open concerns. Please check the comments (TODO:) where further clarification is required. |
Member
|
@punxrok Man, I'm sorry, but would you mind rebasing this on main? And I will get this into a release very soon. |
added 2 commits
August 4, 2025 19:35
# Conflicts: # src/Transports/Pulsar/Wolverine.Pulsar/PulsarEndpoint.cs # src/Transports/Pulsar/Wolverine.Pulsar/PulsarListener.cs # src/Transports/Pulsar/Wolverine.Pulsar/PulsarTransportExtensions.cs # src/Transports/Pulsar/Wolverine.Pulsar/Wolverine.Pulsar.csproj # src/Wolverine/Runtime/MessageContext.cs
8 tasks
# Conflicts: # src/Transports/Pulsar/Wolverine.Pulsar/PulsarTransportExtensions.cs
Co-authored-by: punxrok <6354783+punxrok@users.noreply.github.com> # Conflicts: # src/Transports/Pulsar/Wolverine.Pulsar.Tests/Wolverine.Pulsar.Tests.csproj # src/Transports/Pulsar/Wolverine.Pulsar/Wolverine.Pulsar.csproj
…guidelines Co-authored-by: punxrok <6354783+punxrok@users.noreply.github.com>
…y constant Co-authored-by: punxrok <6354783+punxrok@users.noreply.github.com>
Pulsar: stabilize native retry/DLQ, add tests - Fix PulsarListener resiliency logic, ack handling, and exception headers - Add retry consumer tracking and IPv4 URL for Podman tests - Disable parallelization for Pulsar integration tests - Add unit tests for resiliency config - Verify PulsarNativeReliabilityTests pass under Podman
…ests The tests were failing due to a race condition where the tracking session completed before all requeued messages were processed, resulting in 0 requeued messages being tracked instead of the expected count.
Author
|
Hey @jeremydmiller, sorry for such a late reply. I rebased it as you requested (old commits were made on old 4.* Wolverine branch). |
Member
|
@punxrok Hey man, I'm so, so sorry this slipped. I'll try to get this in tomorrow for 5.13. |
Member
|
I'll deal w/ the rebase after your last commits |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Pulsar support for retry and DLQ