[HDFS-11609] Some blocks can be permanently lost if nodes are decommissioned while dead

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.7.0
• Fix Version/s: 2.9.0, 2.7.4, 3.0.0-alpha4, 2.8.2
• Component/s: namenode
• Target Version/s: 2.7.4, 2.8.1
• Hadoop Flags: Reviewed
• Assignee: Kihwal Lee
• Reporter: Kihwal Lee
• Created: 31/Mar/17 18:30
• Updated: 02/Oct/19 17:14
• Resolved: 01/May/17 19:37

Description

When all the nodes containing a replica of a block are decommissioned while they are dead, they get decommissioned right away even if there are missing blocks. This behavior was introduced by HDFS-7374.

The problem starts when those decommissioned nodes are brought back online. The namenode no longer shows missing blocks, which creates a false sense of cluster health. When the decommissioned nodes are removed and reformatted, the block data is permanently lost. The namenode will report missing blocks after the heartbeat recheck interval (e.g. 10 minutes) from the moment the last node is taken down.

There are multiple issues in the code. As some cause different behaviors in testing vs. production, it took a while to reproduce it in a unit test. I will present analysis and proposal soon.

Issue Links

• is related to: HDFS-10495 Block should be marked as missing if the all the replicas are on Decommissioned nodes.
• relates to: HDFS-7374 Allow decommissioning of dead DataNodes