[ 
https://issues.apache.org/jira/browse/HDFS-15855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18042658#comment-18042658
 ] 

ASF GitHub Bot commented on HDFS-15855:
---------------------------------------

github-actions[bot] commented on PR #2741:
URL: https://github.com/apache/hadoop/pull/2741#issuecomment-3609383317

   We're closing this stale PR because it has been open for 100 days with no 
activity. This isn't a judgement on the merit of the PR in any way. It's just a 
way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working 
on it, please feel free to re-open it and ask for a committer to remove the 
stale tag and review again.
   Thanks all for your contribution.




> Solve the problem of incorrect EC progress when loading FsImage
> ---------------------------------------------------------------
>
>                 Key: HDFS-15855
>                 URL: https://issues.apache.org/jira/browse/HDFS-15855
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: JiangHua Zhu
>            Assignee: JiangHua Zhu
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: ec_progress.jpg
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> When loading FsImage, if EC information exists, the EC loading display is 
> incorrect during processing.
> FSImageFormatProtobuf#loadInternal() : 
> case ERASURE_CODING:
>            Step step = new Step(StepType.ERASURE_CODING_POLICIES);
>            prog.beginStep(Phase.LOADING_FSIMAGE, step);
>            loadErasureCodingSection(in);
>            prog.endStep(Phase.LOADING_FSIMAGE, step);
>            break;
> StartupProgress is not used here to record EC-related information.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to