HDDS-3542.Ozone chunkinfo CLI cannot connect to OM when run from non-om node. #993
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
…OM leader client node.
mukul1987
approved these changes
May 29, 2020
|
@sadanand48 please trigger new CI check with empty commit: |
isahkemat
pushed a commit
to isahkemat/hadoop-ozone
that referenced
this pull request
Jun 4, 2020
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.
What changes were proposed in this pull request?
The chunkinfo tool was not connecting to OM on a non-om leader client node .The fix here is to use existing ozoneManagerClient instance instead of creating a new one.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3542
How was this patch tested?
Tested manually.