[Cluster] Fix BRPC endpoint conflict in local multi-container deployment #548
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
…ent (apache#547) * Fix BRPC endpoint registration conflict when launching multiple containers in local mode * Add geaflow.executor.thread.max.multiple configuration for thread pool scaling
huhao0926
changed the title
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.
…ent (#547)
What changes were proposed in this pull request?
How was this PR tested?
Verification Steps:
Test local mode with multiple containers (geaflow.container.num=3):
Test with excessive worker threads (geaflow.container.worker.num=170):
Test with proper config (geaflow.executor.thread.max.multiple=50):