Added possibility to process messages for each consumer group independently#1034
Merged
yang-xiaodong merged 6 commits intodotnetcore:masterfrom Nov 5, 2021
Merged
Added possibility to process messages for each consumer group independently#1034yang-xiaodong merged 6 commits intodotnetcore:masterfrom
yang-xiaodong merged 6 commits intodotnetcore:masterfrom
Conversation
dario-l
commented
Nov 4, 2021
Contributor
Author
|
Great, thanks 😃 👍🏻 |
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
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.
This addition do not change anything to default behavior of CAP.
To run processing messages for each consumer group independently must set option
UseDispatchingPerGrouptotrue. This will add to DI containerDispatcherPerGroupinstead of defaultDispatcher.With default
Dispatcherbehavior of CAP is:As you can see
VeryFastProcessingReceiverwaits untilXSlowProcessingReceiverfinishes.With
DispatcherPerGroupbehavior of CAP is:Here we have situation where all subscribers pushes received messages to own dispatching channel. Each channel has set thread count to
ConsumerThreadCountvalue.New feature is used in new sample application
Sample.RabbitMQ.SqlServer.DispatcherPerGroup.