Enable configurable concurrency for pulsar #3330
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
Signed-off-by: yaron2 <schneider.yaron@live.com>
ItalyPaleAle
requested changes
Feb 2, 2024
Signed-off-by: yaron2 <schneider.yaron@live.com>
ItalyPaleAle
reviewed
Feb 2, 2024
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.
Reported by users, the Pulsar component has hardcoded concurrency settings which provides very limited performance at moderate to high scale scenarios, causing bottlenecks and issues.
I'm targeting this for 1.13 as Pulsar is a stable component and this is an issue that prevents a lot of production scenarios. Will merge if we have consensus for a 1.13 release, otherwise i'll target the PR against main branch for 1.14.