HDFS high availability in Hadoop - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start the HDFS NameNode in high availability mode.

Hadoop

hdfs --daemon start [1]

Drag options to blanks, or click blank then click option'

Asecondarynamenode

Bjournalnode

Cdatanode

Dnamenode

Attempts:

3 left

💡 Hint

Common Mistakes

Starting datanode instead of namenode

Starting secondarynamenode which is not used in HA

Starting journalnode which is for shared edits

The NameNode is the master node in HDFS and must be started to enable high availability.

2fill in blank

medium

Complete the command to check the status of the HDFS high availability setup.

Hadoop

hdfs haadmin -[1]

Drag options to blanks, or click blank then click option'

AgetServiceState

Bfailover

CtransitionToActive

DrefreshNodes

Attempts:

3 left

💡 Hint

Common Mistakes

Using failover which triggers failover instead of checking status

Using transitionToActive which changes state

Using refreshNodes which refreshes datanode info

The getServiceState option shows if a NameNode is active or standby in HA.

3fill in blank

hard

Fix the error in the command to perform a manual failover in HDFS HA.

Hadoop

hdfs haadmin -failover [1]

Drag options to blanks, or click blank then click option'

Ann1

Bnn2

Attempts:

3 left

💡 Hint

Common Mistakes

Providing two NameNode names causing syntax error

Using the standby NameNode as source incorrectly

The failover command requires the source NameNode only, not two arguments.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps each NameNode to its HA state.

Hadoop

states = {nn: 'hdfs haadmin -getServiceState ' + nn for nn in {{BLANK_2}}

Drag options to blanks, or click blank then click option'

Ann

B['nn1', 'nn2']

C['nn1', 'nn2', 'nn3']

Dnamenodes

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong variable name in the comprehension

Using an incorrect list of NameNodes

The command uses each NameNode name to get its state, iterating over the list of two NameNodes.

5fill in blank

hard

Fill all three blanks to create a dictionary of NameNodes with their HA states, filtering only active ones.

Hadoop

active_nodes = { [1]: 'hdfs haadmin -getServiceState ' + [2] for [3] in ['nn1', 'nn2'] if 'hdfs haadmin -getServiceState ' + [3] == 'active' }

Drag options to blanks, or click blank then click option'

Ann

Dnode

Attempts:

3 left

💡 Hint

Common Mistakes

Using different variable names inconsistently

Not calling the getServiceState command correctly

The comprehension maps each NameNode to its state, iterating over the list and filtering for active nodes only.

Practice

1. What is the main purpose of HDFS high availability (HA)?

easy

A. To speed up data processing by parallel tasks

B. To avoid downtime by using two active NameNodes

C. To increase storage capacity by adding more DataNodes

D. To encrypt data stored in HDFS automatically

Solution

1. Step 1: Understand HDFS HA concept

   HDFS HA uses two NameNodes to ensure one is always available if the other fails.

2. Step 2: Identify the main goal

   The goal is to avoid downtime, not to increase storage or speed processing.

3. Final Answer:

   To avoid downtime by using two active NameNodes -> Option B

4. Quick Check:

   HDFS HA = Avoid downtime [OK]

Hint: Remember: HA means no downtime with two NameNodes [OK]

Common Mistakes:

• Confusing HA with storage scaling
• Thinking HA speeds up processing
• Assuming HA encrypts data

2. Which component is essential for automatic failover in HDFS high availability?

easy

A. ZooKeeper

B. HDFS DataNode

C. YARN ResourceManager

D. MapReduce JobTracker

Solution

1. Step 1: Identify failover mechanism in HDFS HA

   ZooKeeper coordinates and manages automatic failover between NameNodes.

2. Step 2: Exclude unrelated components

   DataNode stores data, ResourceManager manages resources, JobTracker is for MapReduce jobs, none handle failover.

3. Final Answer:

   ZooKeeper -> Option A

4. Quick Check:

   Failover = ZooKeeper [OK]

Hint: ZooKeeper manages failover in HDFS HA [OK]

Common Mistakes:

• Choosing DataNode as failover manager
• Confusing YARN with failover
• Selecting MapReduce components

3. Given the following simplified HDFS HA configuration snippet, what is the role of dfs.nameservices?

dfs.nameservices=cluster1

medium

A. Lists all DataNodes in the cluster

B. Specifies the IP address of the active NameNode

C. Defines the logical name for the HDFS cluster used by clients

D. Sets the replication factor for data blocks

Solution

1. Step 1: Understand dfs.nameservices meaning

   It defines a logical name for the HDFS cluster, grouping NameNodes under one namespace.

2. Step 2: Eliminate other options

   It does not specify IPs, DataNodes, or replication factors.

3. Final Answer:

   Defines the logical name for the HDFS cluster used by clients -> Option C

4. Quick Check:

   dfs.nameservices = cluster name [OK]

Hint: dfs.nameservices names the cluster logically [OK]

Common Mistakes:

• Thinking it sets IP addresses
• Confusing with DataNode list
• Mixing with replication settings

4. You configured HDFS HA but the failover does not happen automatically. Which configuration is most likely missing?

medium

A. Setting dfs.ha.automatic-failover.enabled to true

B. Increasing the replication factor to 5

C. Adding more DataNodes to the cluster

D. Disabling the NameNode checkpoint

Solution

1. Step 1: Identify failover configuration

   Automatic failover requires dfs.ha.automatic-failover.enabled set to true.

2. Step 2: Exclude unrelated settings

   Replication factor, DataNodes count, and checkpoint settings do not control failover.

3. Final Answer:

   Setting dfs.ha.automatic-failover.enabled to true -> Option A

4. Quick Check:

   Auto failover enabled = true [OK]

Hint: Enable dfs.ha.automatic-failover.enabled for auto failover [OK]

Common Mistakes:

• Changing replication factor to fix failover
• Adding DataNodes expecting failover fix
• Disabling checkpoint thinking it helps failover

5. You want to configure HDFS HA with two NameNodes: nn1 and nn2. Which configuration snippet correctly sets the failover proxy provider for cluster1?

hard

A. dfs.replication=3

B. dfs.nameservices=nn1,nn2

C. dfs.ha.automatic-failover.enabled=false

D. dfs.client.failover.proxy.provider.cluster1=org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider

Solution

1. Step 1: Understand failover proxy provider setting

   This property tells the client how to switch between NameNodes during failover.

2. Step 2: Check correctness of options

   dfs.client.failover.proxy.provider.cluster1=org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider

   correctly sets the proxy provider for cluster1.

   dfs.nameservices=nn1,nn2

   wrongly lists NameNodes as nameservices.

   dfs.ha.automatic-failover.enabled=false

   disables failover.

   dfs.replication=3

   sets replication, unrelated to failover.

3. Final Answer:

   dfs.client.failover.proxy.provider.cluster1=org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider -> Option D

4. Quick Check:

   Failover proxy provider =

   dfs.client.failover.proxy.provider.cluster1=org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider

   [OK]

Hint: Set failover proxy provider for cluster1 correctly [OK]

Common Mistakes:

• Confusing nameservices with NameNodes list
• Disabling automatic failover by mistake
• Mixing replication with failover settings