[HDFS-7609] Avoid retry cache collision when Standby NameNode loading edits

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.6.1, 2.8.0, 2.7.2, 3.0.0-alpha1
• Component/s: namenode
• Labels: 2.6.1-candidate 2.7.2-candidate
• Hadoop Flags: Reviewed
• Assignee: Ming Ma
• Reporter: Carrey Zhan
• Created: 14/Jan/15 08:38
• Updated: 06/Jan/17 00:46
• Resolved: 29/May/15 18:14

Description

One day my namenode crashed because of two journal node timed out at the same time under very high load, leaving behind about 100 million transactions in edits log.(I still have no idea why they were not rolled into fsimage.)
I tryed to restart namenode, but it showed that almost 20 hours would be needed before finish, and it was loading fsedits most of the time. I also tryed to restart namenode in recover mode, the loading speed had no different.
I looked into the stack trace, judged that it is caused by the retry cache. So I set dfs.namenode.enable.retrycache to false, the restart process finished in half an hour.

I think the retry cached is useless during startup, at least during recover process.

Issue Links

• duplicates: HDFS-10246 Standby NameNode dfshealth.jsp Response very slow