[HDFS-9106] Transfer failure during pipeline recovery causes permanent write failures

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.8.0, 2.7.2, 3.0.0-alpha1
• Target Version/s: 2.8.0, 2.6.5
• Hadoop Flags: Reviewed
• Assignee: Kihwal Lee
• Reporter: Kihwal Lee
• Created: 18/Sep/15 16:27
• Updated: 06/Jan/17 00:55
• Resolved: 28/Sep/15 20:17

Description

When a new node is added to a write pipeline during flush/sync, if the partial block transfer fails, the write will fail permanently without retrying or continuing with whatever is in the pipeline.

The transfer often fails in busy clusters due to timeout. There is no per-packet ACK between client and datanode or between source and target datanodes. If the total transfer time exceeds the configured timeout + 10 seconds (2 * 5 seconds slack), it is considered failed. Naturally, the failure rate is higher with bigger block sizes.

I propose following changes:

• Transfer timeout needs to be different from per-packet timeout.
• transfer should be retried if fails.

Issue Links

• is related to: HDFS-1675 Transfer RBW between datanodes
• is related to: HDFS-8311 DataStreamer.transfer() should timeout the socket InputStream.