Node decommissioning and scaling in Hadoop

Introduction

Node decommissioning helps safely remove a server from a Hadoop cluster without losing data. Scaling adds or removes nodes to match the workload.

When a server needs maintenance or replacement without stopping the cluster

When the data or workload grows and you need more storage or processing power

When you want to reduce costs by removing unused servers

When balancing the cluster to improve performance

When upgrading hardware or software on cluster nodes

Syntax

Hadoop

1. Add nodes to the cluster by updating configuration files and starting services.
2. To decommission a node:
   - Add the node's hostname to the exclude file (e.g., dfs.exclude).
   - Refresh the NameNode with: hdfs dfsadmin -refreshNodes
   - Wait for data to replicate off the node.
   - Stop the node safely after decommission completes.

The exclude file lists nodes to remove safely.

Refreshing nodes tells Hadoop to start decommissioning listed nodes.

Examples

This file lists nodes to be decommissioned.

Hadoop

# Example exclude file content
node1.example.com
node2.example.com

This command tells Hadoop to start decommissioning nodes in the exclude file.

Hadoop

hdfs dfsadmin -refreshNodes

Steps to scale up by adding a new node.

Hadoop

# Adding a new node
# Update configuration with new node hostname
# Start DataNode service on new node

Sample Program

This script shows how to safely remove a node from a Hadoop cluster.

Hadoop

# This is a shell script example to decommission a node
# Step 1: Add node to exclude file
 echo 'node3.example.com' >> /etc/hadoop/conf/dfs.exclude

# Step 2: Refresh nodes
 hdfs dfsadmin -refreshNodes

# Step 3: Check decommission status
 hdfs dfsadmin -report

# Step 4: After decommission completes, stop DataNode on node3
 ssh node3.example.com 'sudo systemctl stop hadoop-hdfs-datanode'

# Step 5: Remove node3 from cluster configuration if desired

Important Notes

Decommissioning can take time depending on data size to replicate.

Always monitor cluster health during scaling or decommissioning.

Scaling down requires careful planning to avoid data loss.

Summary

Node decommissioning safely removes nodes without data loss.

Scaling adjusts cluster size to workload needs.

Use exclude files and refresh commands to manage nodes.

Practice

1. What is the main purpose of node decommissioning in a Hadoop cluster?

easy

A. To safely remove a node without losing data

B. To add more nodes to the cluster

C. To restart all nodes simultaneously

D. To backup data from the cluster

Solution

1. Step 1: Understand node decommissioning

   Node decommissioning is the process of removing a node from the cluster safely.

2. Step 2: Identify the purpose

   The goal is to ensure no data loss while removing the node.

3. Final Answer:

   To safely remove a node without losing data -> Option A

4. Quick Check:

   Node decommissioning = safe node removal [OK]

Hint: Decommission means safe removal without data loss [OK]

Common Mistakes:

• Confusing decommissioning with adding nodes
• Thinking it restarts nodes
• Assuming it backs up data

2. Which command is used to refresh the list of nodes after updating the exclude file for decommissioning?

easy

A. hdfs namenode -format

B. hdfs dfsadmin -refreshNodes

C. hdfs datanode -report

D. hdfs fsck /

Solution

1. Step 1: Identify the command for refreshing nodes

   After updating the exclude file, the cluster needs to refresh node status.

2. Step 2: Match the correct command

   The command hdfs dfsadmin -refreshNodes tells the NameNode to reload the exclude file.

3. Final Answer:

   hdfs dfsadmin -refreshNodes -> Option B

4. Quick Check:

   Refresh nodes command = dfsadmin -refreshNodes [OK]

Hint: Refresh nodes after exclude file update with dfsadmin -refreshNodes [OK]

Common Mistakes:

• Using namenode -format which erases metadata
• Confusing datanode -report with refresh
• Running fsck which checks file system health

3. Given the following exclude file content:
node1.example.com node3.example.com
and the cluster nodes are node1, node2, node3, node4.
After running hdfs dfsadmin -refreshNodes, which nodes will be decommissioned?

medium

A. All nodes

B. node2 and node4

C. node1, node2, node3

D. node1 and node3

Solution

1. Step 1: Understand exclude file role

   The exclude file lists nodes to be decommissioned.

2. Step 2: Identify nodes in exclude file

   Nodes node1.example.com and node3.example.com are listed, so these two will be decommissioned.

3. Final Answer:

   node1 and node3 -> Option D

4. Quick Check:

   Exclude file nodes = decommissioned nodes [OK]

Hint: Exclude file lists nodes to decommission [OK]

Common Mistakes:

• Assuming nodes not in exclude file are decommissioned
• Thinking all nodes are decommissioned
• Confusing node hostnames

4. You updated the exclude file to remove a node but forgot to run hdfs dfsadmin -refreshNodes. What is the likely result?

medium

A. The node remains active and is not decommissioned

B. The node is immediately decommissioned

C. The cluster shuts down

D. The exclude file is ignored and deleted

Solution

1. Step 1: Understand refreshNodes role

   The refreshNodes command tells the NameNode to reload the exclude file.

2. Step 2: Consequence of not running refresh

   If refreshNodes is not run, the NameNode does not know about the updated exclude file, so the node stays active.

3. Final Answer:

   The node remains active and is not decommissioned -> Option A

4. Quick Check:

   No refreshNodes = no decommission [OK]

Hint: Always run refreshNodes after exclude file update [OK]

Common Mistakes:

• Assuming node decommissions automatically
• Thinking cluster shuts down
• Believing exclude file deletes itself

5. You want to scale your Hadoop cluster by adding 3 new nodes and safely remove 2 old nodes. Which sequence of actions is correct?

hard

A. Add new nodes, restart cluster, update exclude file

B. Add new nodes, update exclude file with old nodes, run hdfs dfsadmin -refreshNodes

C. Update exclude file with old nodes, run hdfs dfsadmin -refreshNodes, add new nodes

D. Remove old nodes physically, then add new nodes

Solution

1. Step 1: Decommission old nodes first

   Update the exclude file with old nodes to remove and run refreshNodes to start decommissioning safely.

2. Step 2: Add new nodes after old nodes are decommissioned

   Once old nodes are safely removed, add new nodes to scale the cluster.

3. Final Answer:

   Update exclude file with old nodes, run hdfs dfsadmin -refreshNodes, add new nodes -> Option C

4. Quick Check:

   Decommission old nodes before adding new ones [OK]

Hint: Decommission old nodes before adding new ones [OK]

Common Mistakes:

• Adding new nodes before decommissioning old ones
• Physically removing nodes without decommissioning
• Restarting cluster unnecessarily