Rack awareness in HDFS in Hadoop - Mini Project: Build & Apply

Rack Awareness in HDFS

📖 Scenario: You are working with a Hadoop cluster that has multiple racks. To improve data reliability and network efficiency, Hadoop uses rack awareness to decide where to place data blocks.Imagine you have a small cluster with nodes distributed across two racks. You want to simulate how Hadoop places data blocks considering rack awareness.

🎯 Goal: Build a simple Python simulation that models rack awareness in HDFS by assigning data blocks to nodes on different racks to ensure fault tolerance.

📋 What You'll Learn

Create a dictionary representing nodes and their racks

Set a replication factor for data blocks

Write logic to assign replicas to nodes ensuring replicas are on different racks

Print the final assignment of data blocks to nodes

💡 Why This Matters

🌍 Real World

Rack awareness in HDFS helps improve data reliability and network efficiency by spreading data copies across different racks to avoid data loss if a rack fails.

💼 Career

Understanding rack awareness is important for Hadoop administrators and data engineers to optimize cluster configuration and ensure fault tolerance.

1

Create the cluster node to rack mapping

Create a dictionary called nodes with these exact entries: 'node1': 'rack1', 'node2': 'rack1', 'node3': 'rack2', 'node4': 'rack2'.

Hadoop

# Create the nodes dictionary mapping nodes to racks
# Your code here

Hint

Use a Python dictionary with node names as keys and rack names as values.

2

Set the replication factor

Create a variable called replication_factor and set it to 3.

Hadoop

nodes = {'node1': 'rack1', 'node2': 'rack1', 'node3': 'rack2', 'node4': 'rack2'}
# Set the replication factor to 3
# Your code here

Hint

Just assign the number 3 to the variable replication_factor.

3

Assign replicas to nodes ensuring rack awareness

Write code to create a list called replica_nodes that contains exactly replication_factor nodes selected from nodes such that no two nodes are from the same rack. Use a simple approach to pick nodes from different racks.

Hadoop

nodes = {'node1': 'rack1', 'node2': 'rack1', 'node3': 'rack2', 'node4': 'rack2'}
replication_factor = 3
# Select replica_nodes list with nodes from different racks
# Your code here

Hint

Use a loop over nodes.items() and keep track of racks used to avoid duplicates.

4

Print the replica node assignments

Write a print statement to display the list replica_nodes.

Hadoop

nodes = {'node1': 'rack1', 'node2': 'rack1', 'node3': 'rack2', 'node4': 'rack2'}
replication_factor = 3

replica_nodes = []
racks_used = set()
for node, rack in nodes.items():
    if rack not in racks_used:
        replica_nodes.append(node)
        racks_used.add(rack)
    if len(replica_nodes) == replication_factor:
        break

# Print the replica_nodes list
# Your code here

Hint

The output should be a list of nodes from different racks. Since replication_factor is 3 but only 2 racks exist, the list will have 2 nodes.

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