Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Duplicate
-
None
-
None
-
None
Description
From investigations and a few test occurrences, the NameNode BlockPlacementPolicy’s considerLoad can be bad for small test clusters.
A small (1-node) cluster may trigger a corner case of maxLoad = 0. In this case, filtering should not take place.
When there is no heartbeat, maxLoad will be 0 and the existing logic will filter out many nodes that have workload, which should be avoided.
Attachments
Attachments
Issue Links
- Blocked
-
HDFS-13833 Improve BlockPlacementPolicyDefault's consider load logic
- Resolved