[
https://issues.apache.org/jira/browse/HDFS-17711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914532#comment-17914532
]
ASF GitHub Bot commented on HDFS-17711:
---------------------------------------
Last-remote11 opened a new pull request, #7299:
URL: https://github.com/apache/hadoop/pull/7299
### Description of PR
When the name node is restarted with dfs.image.parallel.load enabled, the
progress percentage(at namenode web) is reflacted after each thread finished
after fsimage loading.
For example, if dfs.image.parallel.target.sections=12(default), the
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:
- [x] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [x] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> Change fsimage loading progress percentage discontinuous to continuous
> ----------------------------------------------------------------------
>
> Key: HDFS-17711
> URL: https://issues.apache.org/jira/browse/HDFS-17711
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 3.4.1
> Reporter: Sungdong Kim
> Assignee: Sungdong Kim
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.5.0
>
>
> When the name node is restarted with dfs.image.parallel.load enabled, the
> progress percentage(at namenode web) is reflacted after each thread finished
> after fsimage loading.
> For example, if dfs.image.parallel.target.sections=12(default), the
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
