[HDFS-17061] EC: Let data blocks and parity blocks on DNs more balanced

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: balancer & mover, erasure-coding, hdfs
• Target Version/s: 3.5.0
• Assignee: Unassigned
• Reporter: WangYuanben
• Created: 27/Jun/23 12:24
• Updated: 04/Jan/24 08:01

Description

When choosing DN for placing data block or parity block, the existing number of data block and parity block on datanode is not taken into consideration. This may lead to uneven traffic load.

As shown in the figure 1, when reading block group A, B, C, D and E from five different EC files without any missing block, datanodes like DN1 and DN2 will have high traffic load. However, datanodes like DN3, DN4 and DN5 may have low or even no traffic load.

If we can let data blocks and parity blocks on DNs more balanced, the traffic load in cluster will be more balanced and the peak traffic load on DN will be reduced. Here "balance" refers to the matching of the number of data blocks and parity blocks on DN with its EC policy. In the ideal state, each DN has a balanced traffic load just like what figure 2 shows.

Then how to reduce this imbalance? I think it's related to EC policy and the ratio of data blocks to parity blocks on datanode. For RS-3-2-1024k, it's appropriate to let the ratio close to 3:2.

There are two solutions:
1.Improve the block placement policy.
2.Improve the Balancer.