HDDS-9542. Ozone debug chunkinfo command shows incorrect number of entries #5703
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?
If we stop one or more replica datanodes of a key and then run the "ozone debug chunkinfo" command for that key then we get an Execution exception,
because we don't get any container response as we have shut down the datanode and so the pipeline is closed. The exception goes away when the dead node interval is met, i.e. after the datanode is marked closed a new pipeline is created. With this PR, we would be showing the Execution exception but will continue printing other node's getBlock result.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9542
How was this patch tested?
Tested on a cluster.
Configs set:
When all DN's were up,
When one of the replica DN went down,
We got the exception but still printing other blocks location on remaning DN's