[INLONG-10438][Manager] GetConfig does not throw an exception when obtaining the zk address fails #10439
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
…taining the zk address fails
dockerzhang
approved these changes
Jun 17, 2024
aloyszhang
approved these changes
Jun 17, 2024
justinwwhuang
approved these changes
Jun 17, 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.
Fixes #10438
Motivation
GetConfig does not throw an exception when obtaining the zk address fails.
When the getconfig interface does not obtain the zk address, the agent will use local configuration.
Modifications
GetConfig does not throw an exception when obtaining the zk address fails.