Incoming channel concurrency #2382
Merged
Conversation
This file contains 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
|
I had a quick look - it looks good. |
cescoffier
reviewed
Nov 21, 2023
ozangunalp
force-pushed
the
incoming_channel_concurrency
branch
from
51ddf35
to
15a3c59
Compare
Create multiple copies of the configured channel in order to increase the processing concurrency on non-blocking processing Each inbound connector channel would dispatch messages accordingly
…e found per channel
ozangunalp
force-pushed
the
incoming_channel_concurrency
branch
from
15a3c59
to
f3feeed
Compare
cescoffier
approved these changes
Nov 23, 2023
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.
Create multiple copies of the configured channel using, ex.
mp.messaging.incoming.data.concurrency=4config,in order to increase the processing concurrency on non-blocking processing
Attributes per copy-channels can be configured using the channel name with
$separator, ex.mp.messaging.incoming.data$1.attribute=...Each inbound connector channel would dispatch messages accordingly. Connectors based on Vert.x will create separate event loops per channel to dispatch messages. Without the
concurrencyattribute the current behaviour won't change.