[ https://issues.apache.org/jira/browse/HDFS-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Srinivas resolved HDFS-5367. ----------------------------------- Resolution: Fixed Fix Version/s: 1.3.0 Hadoop Flags: Reviewed I committed the patch to branch-1. Thank you John Zhao. > Restoring namenode storage locks namenode due to unnecessary fsimage write > -------------------------------------------------------------------------- > > Key: HDFS-5367 > URL: https://issues.apache.org/jira/browse/HDFS-5367 > Project: Hadoop HDFS > Issue Type: Improvement > Affects Versions: 1.2.1 > Reporter: zhaoyunjiong > Assignee: zhaoyunjiong > Fix For: 1.3.0 > > Attachments: HDFS-5367-branch-1.2.patch > > > 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)