You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Sungdong Kim (Jira)" <ji...@apache.org> on 2025/01/19 15:29:00 UTC
[jira] [Updated] (HDFS-17711) Change fsimage loading progress percentage discontinuous to continuous
[ https://issues.apache.org/jira/browse/HDFS-17711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sungdong Kim updated HDFS-17711:
--------------------------------
Summary: Change fsimage loading progress percentage discontinuous to continuous (was: Progress percentage grows discontinuous when fsimage loading)
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org