Hadoop in cloud (EMR, Dataproc, HDInsight) - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to launch an EMR cluster using AWS CLI.

Hadoop

aws emr create-cluster --name MyCluster --release-label emr-6.3.0 --applications Name=Hadoop [1]

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

A--region us-west-2

B--instance-count 3

C--instance-type m5.xlarge

D--log-uri s3://my-logs/

Attempts:

3 left

💡 Hint

Common Mistakes

Using --instance-type instead of --instance-count

Forgetting to specify the number of instances

The --instance-count option specifies the number of EC2 instances in the EMR cluster.

2fill in blank

medium

Complete the code to submit a Hadoop job on Google Dataproc.

Hadoop

gcloud dataproc jobs submit hadoop --cluster my-cluster --region us-central1 --jar myjob.jar [1]

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

A--zone us-central1-a

B--num-workers 5

C--class com.example.MyJob

D--project my-project

Attempts:

3 left

💡 Hint

Common Mistakes

Using --num-workers which is for cluster size, not job submission

Omitting the main class option

The --class option specifies the main class of the Hadoop job to run.

3fill in blank

hard

Fix the error in the HDInsight script to create a Hadoop cluster with 4 worker nodes.

Hadoop

az hdinsight create --name mycluster --resource-group mygroup --type Hadoop --location eastus [1]

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

A--worker-node-count 4

B--worker-node-size Standard_D3_v2

C--head-node-size Standard_D3_v2

D--cluster-tier Standard

Attempts:

3 left

💡 Hint

Common Mistakes

Using --worker-node-size which sets size, not count

Forgetting to specify worker node count

The --worker-node-count option sets the number of worker nodes in the HDInsight cluster.

4fill in blank

hard

Fill both blanks to configure a Dataproc cluster with 3 master nodes and 5 worker nodes.

Hadoop

gcloud dataproc clusters create my-cluster --region us-central1 --num-masters=[1] --num-workers=[2]

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

A3

B5

C2

D4

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping master and worker counts

Using incorrect numbers for nodes

The --num-masters option sets master nodes, and --num-workers sets worker nodes.

5fill in blank

hard

Fill all three blanks to create an EMR cluster with Hadoop, specify instance type, and enable debugging.

Hadoop

aws emr create-cluster --name TestCluster --release-label emr-6.3.0 --applications Name=[1] --instance-type [2] --enable-debugging [3]

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

AHadoop

Bm5.xlarge

C--log-uri s3://my-emr-logs/

DSpark

Attempts:

3 left

💡 Hint

Common Mistakes

Using Spark instead of Hadoop for the application

Omitting the log URI for debugging

Using wrong instance type

Specify Hadoop as the application, m5.xlarge as instance type, and provide a log URI to enable debugging logs.

Practice

1. Which cloud service is NOT commonly used to run Hadoop clusters in the cloud?

easy

A. AWS EMR

B. Google Dataproc

C. Azure HDInsight

D. Firebase Realtime Database

Solution

1. Step 1: Identify common Hadoop cloud services

   AWS EMR, Google Dataproc, and Azure HDInsight are popular cloud services for Hadoop clusters.

2. Step 2: Recognize Firebase's purpose

   Firebase Realtime Database is a NoSQL database service, not a Hadoop cluster service.

3. Final Answer:

   Firebase Realtime Database -> Option D

4. Quick Check:

   Hadoop clusters use EMR, Dataproc, HDInsight, not Firebase [OK]

Hint: Remember: Firebase is for databases, not Hadoop clusters [OK]

Common Mistakes:

• Confusing Firebase with Hadoop services
• Thinking all cloud services support Hadoop
• Mixing database services with cluster services

2. Which of the following is the correct way to start an AWS EMR cluster using AWS CLI?

easy

A. aws emr launch --cluster TestCluster --app Hadoop

B. aws emr create-cluster --name "TestCluster" --release-label emr-6.5.0 --applications Name=Hadoop

C. aws emr start-cluster --cluster-name TestCluster --version 6.5.0

D. aws emr init --name TestCluster --app Hadoop

Solution

1. Step 1: Understand AWS EMR CLI command structure

   The correct command to create a cluster is 'aws emr create-cluster' with parameters for name, release label, and applications.

2. Step 2: Check each option's syntax

   aws emr create-cluster --name "TestCluster" --release-label emr-6.5.0 --applications Name=Hadoop matches the correct syntax. Options A, B, and D use incorrect commands or parameters.

3. Final Answer:

   aws emr create-cluster --name "TestCluster" --release-label emr-6.5.0 --applications Name=Hadoop -> Option B

4. Quick Check:

   Use 'create-cluster' to start EMR clusters [OK]

Hint: Remember: 'create-cluster' starts EMR clusters via CLI [OK]

Common Mistakes:

• Using wrong CLI commands like 'start-cluster'
• Missing required parameters like release-label
• Confusing application names or syntax

3. What will be the output of this Python code snippet using Google Cloud Dataproc API to list clusters?

from google.cloud import dataproc_v1
client = dataproc_v1.ClusterControllerClient()
project_id = "my-project"
region = "us-central1"
clusters = client.list_clusters(project_id=project_id, region=region)
print([cluster.cluster_name for cluster in clusters])

medium

A. A list of cluster names in the 'us-central1' region for 'my-project'

B. A syntax error due to missing import

C. An empty list if no clusters exist

D. A runtime error because 'list_clusters' requires more parameters

Solution

1. Step 1: Understand the code's purpose

   The code uses Google Cloud Dataproc client to list clusters in a project and region.

2. Step 2: Analyze the output

   The print statement extracts cluster names into a list. If clusters exist, it prints their names; otherwise, an empty list.

3. Final Answer:

   A list of cluster names in the 'us-central1' region for 'my-project' -> Option A

4. Quick Check:

   Dataproc list_clusters returns cluster objects with names [OK]

Hint: List clusters returns objects; extract names with list comprehension [OK]

Common Mistakes:

• Assuming list_clusters returns strings directly
• Expecting errors without proper context
• Confusing parameters needed for list_clusters

4. You try to submit a Hadoop job on Azure HDInsight using this command:

hadoop jar example.jar com.example.WordCount input output

But get an error: 'command not found'. What is the likely cause?

medium

A. The input directory does not exist

B. The jar file 'example.jar' is missing

C. Hadoop is not installed or not in PATH on the HDInsight cluster

D. The output directory already exists

Solution

1. Step 1: Understand the error message

   'command not found' means the shell cannot find the 'hadoop' command.

2. Step 2: Identify possible reasons

   This usually happens if Hadoop is not installed or its binary path is not set in the environment PATH variable.

3. Final Answer:

   Hadoop is not installed or not in PATH on the HDInsight cluster -> Option C

4. Quick Check:

   'command not found' means missing executable in PATH [OK]

Hint: Check if 'hadoop' command runs before job submission [OK]

Common Mistakes:

• Assuming jar or input/output issues cause 'command not found'
• Ignoring environment PATH settings
• Confusing runtime errors with command errors

5. You want to run a Hadoop job on AWS EMR that reads data from S3, processes it, and writes output back to S3. Which of these steps is NOT required?

hard

A. Manually install Hadoop on each EMR node after cluster creation

B. Configure the EMR cluster with IAM roles to access S3 buckets

C. Create an EMR cluster with Hadoop installed

D. Submit the Hadoop job referencing S3 paths for input and output

Solution

1. Step 1: Understand EMR cluster setup

   EMR clusters come with Hadoop pre-installed; manual installation is not needed.

2. Step 2: Review required steps for S3 integration

   IAM roles must allow S3 access, and job submission must use S3 paths.

3. Final Answer:

   Manually install Hadoop on each EMR node after cluster creation -> Option A

4. Quick Check:

   EMR auto-installs Hadoop; manual install unnecessary [OK]

Hint: EMR clusters have Hadoop ready; no manual install needed [OK]

Common Mistakes:

• Thinking Hadoop must be installed manually on EMR nodes
• Forgetting to set IAM roles for S3 access
• Using local paths instead of S3 paths in job submission