[HDFS-12136] BlockSender performance regression due to volume scanner edge case

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Won't Fix
• Affects Version/s: 2.8.0
• Component/s: datanode
• Target Version/s: 2.8.6
• Assignee: Daryn Sharp
• Reporter: Daryn Sharp
• Created: 13/Jul/17 17:36
• Updated: 11/Mar/20 17:56
• Resolved: 11/Mar/20 17:56

Description

HDFS-11160 attempted to fix a volume scan race for a file appended mid-scan by reading the last checksum of finalized blocks within the BlockSender ctor. Unfortunately it's holding the exclusive dataset lock to open and read the metafile multiple times Block sender instantiation becomes serialized.

Performance completely collapses under heavy disk i/o utilization or high xceiver activity. Ex. lost node replication, balancing, or decommissioning. The xceiver threads congest creating block senders and impair the heartbeat processing that is contending for the same lock. Combined with other lock contention issues, pipelines break and nodes sporadically go dead.

Issue Links

• is broken by: HDFS-11160 VolumeScanner reports write-in-progress replicas as corrupt incorrectly
• relates to: HDFS-11187 Optimize disk access for last partial chunk checksum of Finalized replica