Remove gen_server behaviour from stream manager (backport #12684) #12685
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
The stream manager does not need to be a gen_server (no cast, no state) and the gen_server can create contention for large stream deployments (some functions make cluster-wide calls that can take some time). (cherry picked from commit 5107fd4)
(cherry picked from commit 1554b74)
(cherry picked from commit 26f941b)
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.
The stream manager does not need to be a gen_server (no cast, no state) and the gen_server can create contention for large stream deployments (some functions make cluster-wide calls that can take some time).
This is an automatic backport of pull request #12684 done by Mergify.