[
https://issues.apache.org/jira/browse/HDFS-17711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914531#comment-17914531
]
ASF GitHub Bot commented on HDFS-17711:
---------------------------------------
Last-remote11 closed pull request #7299: HDFS-17711. Change fsimage loading
progress percentage discontinuous to continuous
URL: https://github.com/apache/hadoop/pull/7299
> 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
> 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
