<a href="../../hadoop-mapreduce-client/hadoop-mapreduce-client-core/MapReduce_Compatibility_Hadoop1_Hadoop2.html">Compatibilty between Hadoop 1.x and Hadoop 2.x</a>
<a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
<img alt="Built by Maven" src="./images/logos/maven-feather.png"/>
</a>
</div>
</div>
<div id="bodyColumn">
<div id="contentBox">
<!-- 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. --><div class="section">
<li><a href="#Upgrading_from_older_release_to_0.23_and_configuring_federation">Upgrading from older release to 0.23 and configuring federation</a></li>
<li><a href="#Adding_a_new_Namenode_to_an_existing_HDFS_cluster">Adding a new Namenode to an existing HDFS cluster</a></li></ul></li>
<li><a href="#Managing_the_cluster">Managing the cluster</a>
<ul>
<li><a href="#Starting_and_stopping_cluster">Starting and stopping cluster</a></li>
<li>Consists of directories, files and blocks</li>
<li>It supports all the namespace related file system operations such as create, delete, modify and list files and directories.</li></ul></li>
<li><b>Block Storage Service</b> has two parts
<ul>
<li>Block Management (which is done in Namenode)
<ul>
<li>Provides datanode cluster membership by handling registrations, and periodic heart beats.</li>
<li>Processes block reports and maintains location of blocks.</li>
<li>Supports block related operations such as create, delete, modify and get block location.</li>
<li>Manages replica placement and replication of a block for under replicated blocks and deletes blocks that are over replicated.</li></ul></li>
<li>Storage - is provided by datanodes by storing blocks on the local file system and allows read/write access.</li></ul>
<p>The prior HDFS architecture allows only a single namespace for the entire cluster. A single Namenode manages this namespace. HDFS Federation addresses limitation of the prior architecture by adding support multiple Namenodes/namespaces to HDFS file system.</p></li></ul></div>
<p>In order to scale the name service horizontally, federation uses multiple independent Namenodes/namespaces. The Namenodes are federated, that is, the Namenodes are independent and don’t require coordination with each other. The datanodes are used as common storage for blocks by all the Namenodes. Each datanode registers with all the Namenodes in the cluster. Datanodes send periodic heartbeats and block reports and handles commands from the Namenodes.</p><img src="./images/federation.gif" alt="HDFS Federation Architecture" />
<p><b>Block Pool</b></p>
<p>A Block Pool is a set of blocks that belong to a single namespace. Datanodes store blocks for all the block pools in the cluster. It is managed independently of other block pools. This allows a namespace to generate Block IDs for new blocks without the need for coordination with the other namespaces. The failure of a Namenode does not prevent the datanode from serving other Namenodes in the cluster.</p>
<p>A Namespace and its block pool together are called Namespace Volume. It is a self-contained unit of management. When a Namenode/namespace is deleted, the corresponding block pool at the datanodes is deleted. Each namespace volume is upgraded as a unit, during cluster upgrade.</p>
<p><b>ClusterID</b></p>
<p>A new identifier <b>ClusterID</b> is added to identify all the nodes in the cluster. When a Namenode is formatted, this identifier is provided or auto generated. This ID should be used for formatting the other Namenodes into the cluster.</p>
<div class="section">
<h4>Key Benefits<a name="Key_Benefits"></a></h4>
<ul>
<li>Namespace Scalability - HDFS cluster storage scales horizontally but the namespace does not. Large deployments or deployments using lot of small files benefit from scaling the namespace by adding more Namenodes to the cluster</li>
<li>Performance - File system operation throughput is limited by a single Namenode in the prior architecture. Adding more Namenodes to the cluster scales the file system read/write operations throughput.</li>
<li>Isolation - A single Namenode offers no isolation in multi user environment. An experimental application can overload the Namenode and slow down production critical applications. With multiple Namenodes, different categories of applications and users can be isolated to different namespaces.</li></ul></div></div>
<p>Federation configuration is <b>backward compatible</b> and allows existing single Namenode configuration to work without any change. The new configuration is designed such that all the nodes in the cluster have same configuration without the need for deploying different configuration based on the type of the node in the cluster.</p>
<p>A new abstraction called <tt>NameServiceID</tt> is added with federation. The Namenode and its corresponding secondary/backup/checkpointer nodes belong to this. To support single configuration file, the Namenode and secondary/backup/checkpointer configuration parameters are suffixed with <tt>NameServiceID</tt> and are added to the same configuration file.</p>
<p><b>Step 1</b>: Add the following parameters to your configuration: <tt>dfs.nameservices</tt>: Configure with list of comma separated NameServiceIDs. This will be used by Datanodes to determine all the Namenodes in the cluster.</p>
<p><b>Step 2</b>: For each Namenode and Secondary Namenode/BackupNode/Checkpointer add the following configuration suffixed with the corresponding <tt>NameServiceID</tt> into the common configuration file.</p>
<p>Choose a unique cluster_id, which will not conflict other clusters in your environment. If it is not provided, then a unique ClusterID is auto generated.</p>
<p><b>Step 2</b>: Format additional namenode using the following command:</p>
<p>Note that the cluster_id in step 2 must be same as that of the cluster_id in step 1. If they are different, the additional Namenodes will not be part of the federated cluster.</p></div>
<div class="section">
<h4>Upgrading from older release to 0.23 and configuring federation<a name="Upgrading_from_older_release_to_0.23_and_configuring_federation"></a></h4>
<p>Older releases supported a single Namenode. Here are the steps enable federation:</p>
<p>Step 1: Upgrade the cluster to newer release. During upgrade you can provide a ClusterID as follows:</p>
<p>If ClusterID is not provided, it is auto generated.</p></div>
<div class="section">
<h4>Adding a new Namenode to an existing HDFS cluster<a name="Adding_a_new_Namenode_to_an_existing_HDFS_cluster"></a></h4>
<p>Follow the following steps:</p>
<ul>
<li>Add configuration parameter <tt>dfs.nameservices</tt> to the configuration.</li>
<li>Update the configuration with NameServiceID suffix. Configuration key names have changed post release 0.20. You must use new configuration parameter names, for federation.</li>
<li>Add new Namenode related config to the configuration files.</li>
<li>Propagate the configuration file to the all the nodes in the cluster.</li>
<li>Start the new Namenode, Secondary/Backup.</li>
<li>Refresh the datanodes to pickup the newly added Namenode by running the following command:
<p>These commands can be run from any node where the HDFS configuration is available. The command uses configuration to determine the Namenodes in the cluster and starts the Namenode process on those nodes. The datanodes are started on nodes specified in the <tt>slaves</tt> file. The script can be used as reference for building your own scripts for starting and stopping the cluster.</p></div>
<div class="section">
<h4>Balancer<a name="Balancer"></a></h4>
<p>Balancer has been changed to work with multiple Namenodes in the cluster to balance the cluster. Balancer can be run using the command:</p>
<li><tt>node</tt> - this is the <i>default</i> policy. This balances the storage at the datanode level. This is similar to balancing policy from prior releases.</li>
<li><tt>blockpool</tt> - this balances the storage at the block pool level. Balancing at block pool level balances storage at the datanode level also.
<p>Note that Balander only balances the data and does not balance the namespace.</p></li></ul></div>
<p>Decommissioning is similar to prior releases. The nodes that need to be decomissioned are added to the exclude file at all the Namenode. Each Namenode decommissions its Block Pool. When all the Namenodes finish decommissioning a datanode, the datanode is considered to be decommissioned.</p>
<p><b>Step 1</b>: To distributed an exclude file to all the Namenodes, use the following command:</p>
<p>The above command uses HDFS configuration to determine the Namenodes configured in the cluster and refreshes all the Namenodes to pick up the new exclude file.</p></div>
<div class="section">
<h4>Cluster Web Console<a name="Cluster_Web_Console"></a></h4>
<p>Similar to Namenode status web page, a Cluster Web Console is added in federation to monitor the federated cluster at <tt>http://<any_nn_host:port>/dfsclusterhealth.jsp</tt>. Any Namenode in the cluster can be used to access this web page.</p>
<p>The web page provides the following information:</p>
<ul>
<li>Cluster summary that shows number of files, number of blocks and total configured storage capacity, available and used storage information for the entire cluster.</li>
<li>Provides list of Namenodes and summary that includes number of files, blocks, missing blocks, number of live and dead data nodes for each Namenode. It also provides a link to conveniently access Namenode web UI.</li>
<li>It also provides decommissioning status of datanodes.</li></ul></div></div></div>