Xiao Liang created HDFS-11295:
---------------------------------
Summary: Check storage remaining instead of node remaining in
BlockPlacementPolicyDefault.chooseReplicaToDelete()
Key: HDFS-11295
URL: https://issues.apache.org/jira/browse/HDFS-11295
Project: Hadoop HDFS
Issue Type: Improvement
Components: namenode
Affects Versions: 2.7.1
Reporter: Xiao Liang
Currently in BlockPlacementPolicyDefault.chooseReplicaToDelete() the logic for
choosing replica to delete is to pick the node with the least free
space(node.getRemaining()), if all hearbeats are within the tolerable heartbeat
interval.
However, a node may have multiple storages and node.getRemaining() is a sum of
the remainings of them, if free space of the storage with the block to be
delete is low, free space of the node could still be high due to other storages
of the node, finally the storage chosen may not be the storage with least free
space.
So using storage.getRemaining() to choose a storage with least free space for
choosing replica to delete may be a better way to balance storage usage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
