Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-13156

HDFS Block Placement Policy - Client Local Rack



    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.9.0, 3.2.0, 3.1.1
    • Fix Version/s: 3.2.0, 3.3.0
    • Component/s: documentation
    • Labels:
    • Hadoop Flags:


      For the common case, when the replication factor is three, HDFS’s placement policy is to put one replica on the local machine if the writer is on a datanode, otherwise on a random datanode, another replica on a node in a different (remote) rack, and the last on a different node in the same remote rack.


      Having just looked over the Default Block Placement code, the way I understand this, is that, there are three basic scenarios:

      1. HDFS client is running on a datanode inside the cluster
      2. HDFS client is running on a node outside the cluster
      3. HDFS client is running on a non-datanode inside the cluster

      The documentation is ambiguous concerning the third scenario. Please correct me if I'm wrong, but the way I understand the code, if there is an HDFS client inside the cluster, but it is not on a datanode, the first block will be placed on a datanode within the set of datanodes available on the local rack and not simply on any random datanode from the set of all datanodes in the cluster.

      That is to say, if one rack has an HDFS Sink Flume Agent on a dedicated node, I should expect that every first block will be written to a random datanode on the same rack as the HDFS Flume agent, assuming the network topology script is written to include this Flume node.

      If that is correct, can the documentation be updated to include this third common scenario?


        1. HDFS-13156-01.patch
          3 kB
          Ayush Saxena



            • Assignee:
              ayushtkn Ayush Saxena
              belugabehr David Mollitor
            • Votes:
              0 Vote for this issue
              5 Start watching this issue


              • Created: