[Host.AzureServiceBus][Host.AzureEventHub] Fix the batch publish chunking iterations #426
+302
−116
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
…king iterations Signed-off-by: Tomasz Maruszak <[email protected]>
|
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.
Summary
Fixes an issue in the Bulk Message Publish API where message chunking could fail at chunk boundaries, causing some messages to be skipped.
Details
The problem occurred because chunking was adaptive - based on the buffer capacity reported by Azure Service Bus (ASB) or Azure Event Hubs (AEH) - and varied with message size. When large batches of messages were published at once via the Bulk Message API, this sometimes resulted in incorrect chunking and message loss at the boundary.
Fix
This PR corrects the chunking logic to ensure all messages are properly published without being skipped.
Affected Transports