[HDFS-10335] Mover$Processor#chooseTarget() always chooses the first matching target storage group

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.8.0
• Fix Version/s: 2.8.0, 2.7.3, 3.0.0-alpha1
• Component/s: balancer & mover
• Target Version/s: 2.8.0
• Hadoop Flags: Reviewed
• Assignee: Mingliang Liu
• Reporter: Mingliang Liu
• Created: 27/Apr/16 02:12
• Updated: 06/Jan/17 00:48
• Resolved: 29/Apr/16 18:29

Description

Currently the org.apache.hadoop.hdfs.server.mover.Mover$Processor#chooseTarget() always chooses the first matching target datanode from the candidate list. This may make the mover schedule a lot of task to a few of the datanodes (first several datanodes of the candidate list). The overall performance will suffer significantly from this because of the saturated network/disk usage. Specially, if the dfs.datanode.balance.max.concurrent.moves is set, the scheduled move task will be queued on a few of the storage group, regardless of other available storage groups. We need an algorithm which can distribute the move tasks approximately even across all the candidate target storage groups.

Thanks szetszwo for offline discussion.