Big Data Hadoop Certification Training
- 154k Enrolled Learners
- Live Class
One of the most attractive features of Hadoop framework is its utilization of commodity hardware. However, this leads to frequent DataNode crashes in a Hadoop cluster. Another striking feature of Hadoop Framework is the ease of scale in accordance to the rapid growth in data volume. Because of these two reasons, one of the most common task of a Hadoop administrator is to commission (Add) and decommission (Remove) Data Nodes in a Hadoop Cluster.
Above diagram shows a step by step process to decommission a DataNode in the cluster.
The first task is to update the ‘exclude‘ files for both HDFS (hdfs-site.xml) and MapReduce (mapred-site.xml).
The ‘exclude’ file:
Here is the sample configuration for the exclude file in hdfs-site.xml and mapred-site.xml:
Note: The full pathname of the files must be specified.
The ‘dfsadmin’ and ‘mradmin’ commands refresh the configuration with the changes to make them aware of the new node.
The ‘slaves’ file on master server contains the list of all data nodes. This must also be updated to ensure any issues in future hadoop daemon start/stop.
The important step in data node commission process is to run the Cluster Balancer.
>hadoop balancer -threshold 40
Balancer attempts to provide a balance to a certain threshold among data nodes by copying block data from older nodes to newly commissioned nodes.
So, this is how you can do – Commissioning and Decommissioning Nodes in a Hadoop Cluster.
Got a question for us? Please mention it in the comments section and we will get back to you.