Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
Sometimes Clients like HBase are required to dynamically compute the datanodes it wishes to place the blocks for a file for higher level of locality. For this purpose there is a need of a way to give the Namenode a hint in terms of a favoredNodes parameter about the locations where the client wants to put each block. The proposed solution is a favored nodes parameter in the addBlock() method and in the create() file method to enable the clients to give the hints to the NameNode about the locations of each replica of the block. Note that this would be just a hint and finally the NameNode would look at disk usage, datanode load etc. and decide whether it can respect the hints or not.
Attachments
Attachments
Issue Links
- is related to
-
HDFS-4778 Invoke getPipeline in the chooseTarget implementation that has favoredNodes
- Closed
-
HDFS-6680 BlockPlacementPolicyDefault does not choose favored nodes correctly
- Closed
-
HDFS-4779 Backport HDFS-2576 to branch-1 (this is the favoredNodes API related changes)
- Open
- is required by
-
HBASE-5843 Improve HBase MTTR - Mean Time To Recover
- Closed
- relates to
-
HDFS-4778 Invoke getPipeline in the chooseTarget implementation that has favoredNodes
- Closed
-
HBASE-4755 HBase based block placement in DFS
- Closed