HDFS-17711. Change fsimage loading progress percentage discontinuous to continuous #7299
+2
−3
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.
Description of PR
When the name node is restarted with dfs.image.parallel.load enabled, the completion percentage(at namenode web) is reflacted after each thread finished after fsimage loading.
For example, if dfs.image.parallel.target.sections=12(default), the completion percentage increases by 0% -> 8.3% (1/12) -> 16.6% (2/12) ->.... -> 100%.
This is because each thread uses a separate counter.
According docs of
org.apache.hadoop.hdfs.server.namenode.startupprogress.getCounter
, the counter guarantees thread-safe, so it seems that each fimage loading thread can use the same counter.How was this patch tested?
run hadoop unit test and tested my test hadoop cluster (version 3.4.0)
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?