[HADOOP-1117] DFS Scalability: When the namenode is restarted it consumes 80% CPU

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.12.0
• Fix Version/s: 0.12.1
• Assignee: Dhruba Borthakur
• Reporter: Dhruba Borthakur
• Created: 13/Mar/07 22:52
• Updated: 16/May/11 21:32
• Resolved: 14/Mar/07 21:20

Description

When the namenode is restarted, the datanodes register and each block is inserted into neededReplication. When the namenode exists, safemode it sees starts processing neededReplication. It picks up a block from neededReplication, sees that it has already has the required number of replicas, and continues to the next block in neededReplication. The blocks remain in neededReplication permanentlyhe namenode worker thread to scans this huge list of blocks once every 3 seconds. This consumes plenty of CPU on the namenode.

Issue Links

• is blocked by: HADOOP-1113 namenode slowdown when orphan block(s) left in neededReplication