Rack awareness in HDFS in Hadoop - Step-by-Step Execution

Concept Flow - Rack awareness in HDFS

Client requests file write

↓

NameNode identifies racks

↓

Select DataNodes on different racks

↓

Write replicas to chosen DataNodes

↓

Client confirms write success

↓

Done

The client asks to write data, the NameNode picks DataNodes on different racks to store replicas, ensuring fault tolerance across racks.

Execution Sample

Hadoop

replica_placement = []
racks = ['rack1', 'rack2', 'rack3']
data_nodes = {'rack1': ['DN1', 'DN2'], 'rack2': ['DN3'], 'rack3': ['DN4', 'DN5']}

for rack in racks:
    replica_placement.append(data_nodes[rack][0])

This code selects one DataNode from each rack to place replicas for fault tolerance.

Execution Table

Step	Rack	DataNode Selected	Replica Placement List	Action
1	rack1	DN1	['DN1']	Select first DataNode from rack1
2	rack2	DN3	['DN1', 'DN3']	Select first DataNode from rack2
3	rack3	DN4	['DN1', 'DN3', 'DN4']	Select first DataNode from rack3
4	-	-	['DN1', 'DN3', 'DN4']	Replica placement complete

💡 All racks processed, replicas placed on one DataNode per rack

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
replica_placement	[]	['DN1']	['DN1', 'DN3']	['DN1', 'DN3', 'DN4']	['DN1', 'DN3', 'DN4']

Key Moments - 3 Insights

Why does HDFS place replicas on different racks?

Placing replicas on different racks protects data if one rack fails, as shown in execution_table rows 1-3 where replicas are chosen from separate racks.

What happens if all replicas are on the same rack?

If all replicas are on the same rack, a rack failure can cause data loss. The code and execution_table show how HDFS avoids this by selecting DataNodes from different racks.

Why do we select only one DataNode per rack in this example?

Selecting one DataNode per rack ensures replicas are spread out. This simple example picks the first DataNode per rack, as seen in the loop in execution_sample and execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, which DataNode is selected from rack2 at step 2?

A DN2

B DN4

C DN3

D DN1

💡 Hint

Check the 'DataNode Selected' column at step 2 in execution_table

At which step is the replica placement complete according to the execution_table?

A Step 3

B Step 4

C Step 2

D Step 1

💡 Hint

Look at the 'Action' column for the step indicating completion

If rack3 had no DataNodes, how would the replica_placement list change after step 3?

A It would have only ['DN1', 'DN3']

B It would have ['DN1', 'DN3', 'DN4']

C It would be empty

D It would have duplicates

💡 Hint

Refer to variable_tracker and consider missing DataNodes in rack3

Concept Snapshot

Rack awareness in HDFS:
- NameNode knows rack locations of DataNodes
- Replicas placed on different racks
- Protects data from rack failure
- Select one DataNode per rack for replicas
- Ensures fault tolerance and availability

Full Transcript

Rack awareness in HDFS means the system knows which DataNodes belong to which racks. When a client writes data, the NameNode chooses DataNodes on different racks to store replicas. This spreads copies across racks to protect against rack failures. The example code shows selecting one DataNode from each rack. The execution table traces this selection step-by-step, showing the replica placement list growing as each rack is processed. Key moments clarify why spreading replicas matters and how the selection works. The visual quiz tests understanding of which DataNodes are chosen and what happens if racks lack DataNodes. The snapshot summarizes the main points for quick review.

Practice

1. What is the main purpose of rack awareness in HDFS?

easy

A. To place data replicas on different racks to improve fault tolerance

B. To store all data replicas on the same rack for faster access

C. To reduce the number of data replicas stored in the cluster

D. To encrypt data before storing it in HDFS

Solution

1. Step 1: Understand rack awareness concept

   Rack awareness means placing data copies on different racks to avoid data loss if one rack fails.

2. Step 2: Identify the main goal

   The goal is to improve fault tolerance by spreading replicas across racks.

3. Final Answer:

   To place data replicas on different racks to improve fault tolerance -> Option A

4. Quick Check:

   Rack awareness = fault tolerance [OK]

Hint: Think about protecting data from rack failures [OK]

Common Mistakes:

• Assuming all replicas are on the same rack
• Confusing rack awareness with encryption
• Thinking rack awareness reduces replica count

2. Which of the following is the correct way to configure rack awareness in HDFS?

easy

A. Implement a script that maps nodes to racks and set net.topology.script.file.name

B. Disable rack awareness by setting dfs.rack.awareness.enabled to false

C. Set the property dfs.replication to 1

D. Use hdfs dfs -put command with rack option

Solution

1. Step 1: Identify rack awareness configuration

   Rack awareness requires a script that maps nodes to racks.

2. Step 2: Recognize the correct property

   The property net.topology.script.file.name points to this script.

3. Final Answer:

   Implement a script that maps nodes to racks and set net.topology.script.file.name -> Option A

4. Quick Check:

   Rack mapping script = net.topology.script.file.name [OK]

Hint: Rack awareness needs a node-to-rack mapping script [OK]

Common Mistakes:

• Setting replication to 1 disables replication, not rack awareness
• Using HDFS commands with rack options (not supported)
• Disabling rack awareness removes its benefits

3. Given a Hadoop cluster with 3 racks and replication factor 3, how does HDFS place replicas for a block?

medium

A. One replica on the local node, and the other two on different racks

B. Replicas are placed randomly without rack consideration

C. All 3 replicas on the same rack

D. One replica on the local node, one on a different rack, and one on the same rack but different node

Solution

1. Step 1: Recall HDFS replica placement policy

   HDFS places one replica on the local node, one replica on a different rack, and the third replica on the same rack but a different node to balance fault tolerance and network usage.

2. Step 2: Apply to 3 racks and replication factor 3

   One replica is local, one is on a different rack, and the third is on the same rack but different node.

3. Final Answer:

   One replica on the local node, one on a different rack, and one on the same rack but different node -> Option D

4. Quick Check:

   Replica placement = local + different rack + same rack different node [OK]

Hint: One local replica, one different rack, one same rack different node [OK]

Common Mistakes:

• Placing all replicas on the same rack
• Placing two replicas on the same rack as local
• Ignoring rack awareness in placement

4. You configured rack awareness but notice all replicas are stored on the same rack. What is the likely cause?

medium

A. Replication factor is set to 1

B. The rack awareness script is missing or misconfigured

C. HDFS does not support rack awareness

D. Data nodes are all physically on the same rack

Solution

1. Step 1: Check rack awareness setup

   If all replicas are on the same rack, the rack awareness script might be missing or incorrect, so HDFS cannot identify racks properly.

2. Step 2: Rule out other causes

   Replication factor 1 means only one replica, so multiple replicas on same rack is not possible. HDFS supports rack awareness. If all nodes are on the same rack physically, then placement is expected.

3. Final Answer:

   The rack awareness script is missing or misconfigured -> Option B

4. Quick Check:

   Missing script = replicas on same rack [OK]

Hint: Check rack script if replicas cluster on one rack [OK]

Common Mistakes:

• Assuming replication factor 1 causes multiple replicas
• Ignoring physical rack layout
• Believing HDFS lacks rack awareness support

5. In a cluster with only two racks and replication factor 3, how does HDFS handle rack awareness when placing replicas?

hard

A. Places replicas randomly ignoring rack awareness due to limited racks

B. Places all replicas on the same rack because there are only two racks

C. Places one replica on each rack and the third replica on any rack to maximize availability

D. Fails to store replicas because rack count is less than replication factor

Solution

1. Step 1: Understand rack awareness with limited racks

   When racks are fewer than replication factor, HDFS tries to spread replicas across racks as much as possible.

2. Step 2: Apply to 2 racks and replication factor 3

   HDFS places one replica on each rack, and the third replica on any rack to ensure three copies exist.

3. Final Answer:

   Places one replica on each rack and the third replica on any rack to maximize availability -> Option C

4. Quick Check:

   Limited racks = spread as much as possible [OK]

Hint: With fewer racks, spread replicas as much as possible [OK]

Common Mistakes:

• Thinking all replicas must be on different racks always
• Assuming failure if racks < replication factor
• Ignoring partial rack spreading