fix a config error in RegionAware#initialize #4098
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
AnonHxy
approved these changes
Oct 7, 2023
|
LGTM |
hangc0276
approved these changes
Oct 7, 2023
|
It's better to add more description about the changes. Or add a link to the method. So it's can better be understood by the reviewer. |
|
@zymap Has added more description. This is a small fix |
|
rerun failure checks |
Ghatage
pushed a commit
to sijie/bookkeeper
that referenced
this pull request
Jul 12, 2024
Co-authored-by: fanjianye <fanjianye@bigo.sg> ### Motivation fix a config error in RegionAware#initialize. There is double config ignoreLocalNodeInPlacementPolicy in RegionAware#initialize. Actually one of the config is useHostnameResolveLocalNodePlacementPolicy. ### change use correct config name
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.
Motivation
fix a config error in RegionAware#initialize.
There is double config ignoreLocalNodeInPlacementPolicy in RegionAware#initialize. Actually one of
the config is useHostnameResolveLocalNodePlacementPolicy.
change
use correct config name