[ 
https://issues.apache.org/jira/browse/HDFS-16245?focusedWorklogId=659217&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-659217
 ]

ASF GitHub Bot logged work on HDFS-16245:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 02/Oct/21 11:35
            Start Date: 02/Oct/21 11:35
    Worklog Time Spent: 10m 
      Work Description: jianghuazhu opened a new pull request #3512:
URL: https://github.com/apache/hadoop/pull/3512


   …ode service.
   
   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'HADOOP-17799. Your PR title ...'.
   -->
   
   ### Description of PR
   
   
   ### How was this patch tested?
   
   
   ### For code changes:
   
   - [ ] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] 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?
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 659217)
    Remaining Estimate: 0h
            Time Spent: 10m

> Record the number of INodeDirectory when loading the FSImage file
> -----------------------------------------------------------------
>
>                 Key: HDFS-16245
>                 URL: https://issues.apache.org/jira/browse/HDFS-16245
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: JiangHua Zhu
>            Assignee: JiangHua Zhu
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When starting parallel loading of FsImage (dfs.image.parallel.load=true), you 
> can see in the startup log that the number of loaded INodes has been printed, 
> but it is impossible to know the specific number of loaded INodeDirectory, 
> because it is not printed now.
> For example, here are some startup information:
> 2021-09-30 19:12:55,012 [15587]-INFO 
> [main:FSImageFormatProtobuf$Loader@340]-The fsimage will be loaded in 
> parallel using 4 threads
> 2021-09-30 19:12:55,031 [15606]-INFO 
> [main:FSImageFormatPBINode$Loader@418]-Loading the INode section in parallel 
> with 12 sub-sections
> 2021-09-30 19:12:55,034 [15609]-INFO 
> [main:FSImageFormatPBINode$Loader@409]-Loading xxxx INodes.
> ......
> 2021-09-30 19:30:37,080 [1077655]-INFO 
> [main:FSImageFormatPBINode$Loader@465]-Completed loading all INode sections. 
> Loaded xxxx inodes.
> 2021-09-30 19:30:37,086 [1077661]-INFO 
> [main:FSImageFormatPBINode$Loader@222]-Loading the INodeDirectory section in 
> parallel with 12 sub-sections
> ......
> 2021-09-30 19:36:58,074 [1458649]-INFO 
> [main:FSImageFormatPBINode$Loader@261]-Completed loading all INodeDirectory 
> sub-sections
> 2021-09-30 19:36:58,076 [1458651]-INFO 
> [main:FSImageFormatPBINode$Loader@339]-Completed update blocks map and name 
> cache, total waiting duration 1 ms.
> 2021-09-30 19:36:58,111 [1458686]-INFO 
> [main:FSImageFormatProtobuf$Loader@248]-Loaded FSImage in xxxx seconds.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to