This is an automated email from the ASF dual-hosted git repository.
ayushsaxena pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/hadoop.git
The following commit(s) were added to refs/heads/trunk by this push:
new 17ffcab HDFS-14546. Document block placement policies. Contributed by
Amithsha.
17ffcab is described below
commit 17ffcab5f621400bd8bb47dc8fb29365f6e24ebd
Author: Ayush Saxena <ayushsax...@apache.org>
AuthorDate: Sun Jun 21 17:27:28 2020 +0530
HDFS-14546. Document block placement policies. Contributed by Amithsha.
---
.../site/markdown/HdfsBlockPlacementPolicies.md | 165 +++++++++++++++++++++
.../hadoop-hdfs/src/site/markdown/HdfsDesign.md | 3 +
.../site/resources/images/RackFaultTolerant.jpg | Bin 0 -> 55017 bytes
3 files changed, 168 insertions(+)
diff --git
a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsBlockPlacementPolicies.md
b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsBlockPlacementPolicies.md
new file mode 100644
index 0000000..4550f04
--- /dev/null
+++
b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsBlockPlacementPolicies.md
@@ -0,0 +1,165 @@
+<!---
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License. See accompanying LICENSE file.
+-->
+
+BlockPlacementPolicies
+======================
+<!-- MACRO{toc|fromDepth=0|toDepth=3} -->
+
+##Introduction
+By default HDFS supports BlockPlacementPolicyDefault. Where one block on local
and copy on 2 different nodes of same remote rack. Additional to this HDFS
supports several different pluggable block placement policies. Users can choose
the policy based on their infrastructure and use case. This document describes
the detailed information about the type of policies with its use cases and
configuration.
+
+
+## BlockPlacementPolicyRackFaultTolerant
+
+BlockPlacementPolicyRackFaultTolerant can be used to split the placement of
blocks across multiple rack.By default with replication of 3
BlockPlacementPolicyDefault will put one replica on the local machine if the
writer is on a datanode, otherwise on a random datanode in the same rack as
that of the writer, another replica on a node in a different (remote) rack, and
the last on a different node in the same remote rack. So totally 2 racks will
be used, in sceneraio like 2 racks going do [...]
+
+For more details check
[HDFS-7891](https://issues.apache.org/jira/browse/HDFS-7891)
+
+
+
+ **Configurations :**
+
+- hdfs-site.xml
+
+```xml
+<property>
+ <name>dfs.block.replicator.classname</name>
+
<value>org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicyRackFaultTolerant</value>
+</property>
+```
+
+
+## BlockPlacementPolicyWithNodeGroup
+
+With new 3 layer hierarchical topology, a node group level got introduced,
which maps well onto a infrastructure that is based on a virtulized
environment. In Virtualized environment multiple vm's will be hosted on same
physical machine. Vm's on the same physical host are affected by the same
hardware failure. So mapping the physical host a node groups this block
placement gurantees that it will never place more than one replica on the same
node group (physical host), in case of node gro [...]
+
+ **Configurations :**
+
+- core-site.xml
+
+```xml
+<property>
+ <name>net.topology.impl</name>
+ <value>org.apache.hadoop.net.NetworkTopologyWithNodeGroup</value>
+</property>
+<property>
+ <name>net.topology.nodegroup.aware</name>
+ <value>true</value>
+</property>
+```
+
+- hdfs-site.xml
+
+```xml
+<property>
+ <name>dfs.block.replicator.classname</name>
+ <value>
+
org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicyWithNodeGroup
+ </value>
+</property>
+```
+
+- Topology script
+
+Topology script is the same as the examples above, the only difference is,
+instead of returning only **/{rack}**, the script should return
+**/{rack}/{nodegroup}**. Following is an example topology mapping table:
+
+```
+192.168.0.1 /rack1/nodegroup1
+192.168.0.2 /rack1/nodegroup1
+192.168.0.3 /rack1/nodegroup2
+192.168.0.4 /rack1/nodegroup2
+192.168.0.5 /rack2/nodegroup3
+192.168.0.6 /rack2/nodegroup3
+```
+
+For more details check
[HDFS-8468](https://issues.apache.org/jira/browse/HADOOP-8468)
+
+## BlockPlacementPolicyWithUpgradeDomain
+
+To address the limitation of block placement policy on rolling upgrade, the
concept of upgrade domain has been added to HDFS via a new block placement
policy. The idea is to group datanodes in a new dimension called upgrade
domain, in addition to the existing rack-based grouping. For example, we can
assign all datanodes in the first position of any rack to upgrade domain ud_01,
nodes in the second position to upgrade domain ud_02 and so on.
+It will make sure replicas of any given block are distributed across machines
from different upgrade domains. By default, 3 replicas of any given block are
placed on 3 different upgrade domains. This means all datanodes belonging to a
specific upgrade domain collectively won’t store more than one replica of any
block.
+
+For more details check
[HDFS-9006](https://issues.apache.org/jira/browse/HDFS-9006)
+
+Detailed info about configuration [Upgrade Domain
Policy](HdfsUpgradeDomain.html)
+
+## AvailableSpaceBlockPlacementPolicy
+
+The AvailableSpaceBlockPlacementPolicy is a space balanced block placement
policy. It is similar to BlockPlacementPolicyDefault but will choose low used
percent datanodes for new blocks with a little high possibility.
+
+ **Configurations :**
+
+- hdfs-site.xml
+
+```xml
+<property>
+ <name>dfs.block.replicator.classname</name>
+
<value>org.apache.hadoop.hdfs.server.blockmanagement.AvailableSpaceBlockPlacementPolicy</value>
+</property>
+
+<property>
+
<name>dfs.namenode.available-space-block-placement-policy.balanced-space-preference-fraction</name>
+ <value>0.6</value>
+ <description>
+ Special value between 0 and 1, noninclusive. Increases chance of
+ placing blocks on Datanodes with less disk space used.
+ </description>
+</property>
+
+<property>
+ <name>
+ dfs.namenode.available-space-block-placement-policy.balance-local-node
+ </name>
+ <value>false</value>
+ <description>
+ If true, balances the local node too.
+ </description>
+</property>
+```
+
+For more details check
[HDFS-8131](https://issues.apache.org/jira/browse/HDFS-8131)
+
+## AvailableSpaceRackFaultTolerantBlockPlacementPolicy
+
+The AvailableSpaceRackFaultTolerantBlockPlacementPolicy is a space balanced
block placement policy similar to AvailableSpaceBlockPlacementPolicy. It
extends BlockPlacementPolicyRackFaultTolerant and distributes the blocks
+amongst maximum number of racks possible and at the same time will try to
choose datanodes with low used percent with high probability.
+
+ **Configurations :**
+
+- hdfs-site.xml
+
+```xml
+<property>
+ <name>dfs.block.replicator.classname</name>
+
<value>org.apache.hadoop.hdfs.server.blockmanagement.AvailableSpaceRackFaultTolerantBlockPlacementPolicy</value>
+</property>
+
+<property>
+
<name>dfs.namenode.available-space-rack-fault-tolerant-block-placement-policy.balanced-space-preference-fraction</name>
+ <value>0.6</value>
+ <description>
+ Only used when the dfs.block.replicator.classname is set to
+
org.apache.hadoop.hdfs.server.blockmanagement.AvailableSpaceRackFaultTolerantBlockPlacementPolicy.
+ Special value between 0 and 1, noninclusive. Increases chance of
+ placing blocks on Datanodes with less disk space used. More the value near
1
+ more are the chances of choosing the datanode with less percentage of data.
+ Similarly as the value moves near 0, the chances of choosing datanode with
+ high load increases as the value reaches near 0.
+ </description>
+</property>
+```
+
+For more details check
[HDFS-15288](https://issues.apache.org/jira/browse/HDFS-15288)
\ No newline at end of file
diff --git a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsDesign.md
b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsDesign.md
index ff43e45..894ff7e 100644
--- a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsDesign.md
+++ b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsDesign.md
@@ -139,6 +139,9 @@ then that replica is preferred to satisfy the read request.
If HDFS cluster spans multiple data centers,
then a replica that is resident in the local data center is preferred over any
remote replica.
+### Block Placement Policies
+As mentioned above 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 in the same rack as that of the
writer, another replica on a node in a different (remote) rack, and the last on
a different node in the same remote rack. If the replication factor is greater
than 3, the placement of the 4th and following replicas are determined randomly
while keeping the number of replic [...]
+
### Safemode
On startup, the NameNode enters a special state called Safemode. Replication
of data blocks does not occur when the NameNode is in the Safemode state. The
NameNode receives Heartbeat and Blockreport messages from the DataNodes. A
Blockreport contains the list of data blocks that a DataNode is hosting. Each
block has a specified minimum number of replicas. A block is considered safely
replicated when the minimum number of replicas of that data block has checked
in with the NameNode. After [...]
diff --git
a/hadoop-hdfs-project/hadoop-hdfs/src/site/resources/images/RackFaultTolerant.jpg
b/hadoop-hdfs-project/hadoop-hdfs/src/site/resources/images/RackFaultTolerant.jpg
new file mode 100644
index 0000000..8c05930
Binary files /dev/null and
b/hadoop-hdfs-project/hadoop-hdfs/src/site/resources/images/RackFaultTolerant.jpg
differ
---------------------------------------------------------------------
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org
