[HADOOP-3002] HDFS should not remove blocks while in safemode.

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.16.0
• Fix Version/s: 0.17.2
• Assignee: Konstantin Shvachko
• Reporter: Konstantin Shvachko
• Created: 12/Mar/08 00:49
• Updated: 08/Jul/09 16:42
• Resolved: 08/Jul/08 23:36

Description

I noticed that data-nodes are removing blocks during a rather prolonged distributed upgrade when the name-node is in safe mode.
This happened on my experimental cluster with accelerated block report rate.
By definition in safe mode the name-node should not

• accept client requests to change the namespace state, and
• schedule block replications and/or block removal for the data-nodes.

We don't want any unnecessary replications until all blocks are reported during startup.
We also don't want to remove blocks if safe mode is entered manually.
In heartbeat processing we explicitly verify that the name-node is in safe-mode and do not return any block commands to the data-nodes.
Block reports can also return block commands, which should be banned during safe mode.

Issue Links

• is related to: HADOOP-3677 Problems with generation stamp upgrade
• relates to: HADOOP-3804 NPE in FSNamesystem.addStoredBlock(...)
• relates to: HADOOP-3709 Lock hierarchy violation in namenode while handling hearbeats