Pulsar support for retry and DLQ#1333
Conversation
3.11 update
|
Hey @jeremydmiller |
…s sync with Pulsar RECONSUMETIMES header
…red endpoints, added first test for it
…on waiting for DLQ envelope
… MoveToRetryLetterQueueAsync from the lifecycle
|
@punxrok Couple things:
|
…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
# 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.
|
Hey @jeremydmiller, sorry for such a late reply. I rebased it as you requested (old commits were made on old 4.* Wolverine branch). |
|
@punxrok Hey man, I'm so, so sorry this slipped. I'll try to get this in tomorrow for 5.13. |
|
I'll deal w/ the rebase after your last commits |
|
Totally misspoke, NOW it's going to go in soon. |
|
I'm pulling this in now and fixing whatever is up in main. Looks like just Nuget ref problems so far. |
|
Thanks, @jeremydmiller! No worries about the delay at all. I really appreciate you handling the rebase and those NuGet-related fixes. |
|
@punxrok Appreciate your patience. I do pride myself on getting PRs and issues taken care of reasonably quick, but sometimes things do fall through the cracks |
Pulsar support for retry and DLQ