[
https://issues.apache.org/jira/browse/HDFS-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhaoyunjiong updated HDFS-5367:
-------------------------------
Attachment: HDFS-5367
The fsimage restored when SecondaryNameNode call rollEditLog will be replaced
soon when SecondaryNameNode call rollFsImage.
So I think restore fsimage is not necessary.
> Restore fsimage locked NameNode too long when the size of fsimage are big
> -------------------------------------------------------------------------
>
> Key: HDFS-5367
> URL: https://issues.apache.org/jira/browse/HDFS-5367
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: zhaoyunjiong
> Assignee: zhaoyunjiong
>
> Our cluster have 40G fsimage, we write one copy of edit log to NFS.
> After NFS temporary failed, when doing checkpoint, NameNode try to recover
> it, and it will save 40G fsimage to NFS, it takes some time (> 40G/128MB/s =
> 320 seconds) , and it locked FSNamesystem, and this bring down our cluster.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
