Dataproc for Spark/Hadoop in GCP - Mini Project: Build & Apply

Dataproc Cluster Setup for Spark Job

📖 Scenario: You are working as a cloud engineer for a company that wants to run big data processing jobs using Apache Spark on Google Cloud Platform. Your task is to create a Dataproc cluster, configure it, and submit a Spark job.

🎯 Goal: Build a Dataproc cluster configuration and prepare it to run a Spark job on Google Cloud Platform.

📋 What You'll Learn

Create a Dataproc cluster configuration dictionary with exact keys and values

Add a configuration variable for the cluster region

Write the code to submit a Spark job using the cluster configuration

Complete the cluster creation command with all required parameters

💡 Why This Matters

🌍 Real World

Dataproc clusters are used to run big data processing jobs on Google Cloud Platform, enabling scalable and managed Spark and Hadoop workloads.

💼 Career

Cloud engineers and data engineers often create and manage Dataproc clusters to run data analytics and processing pipelines efficiently.

1

Create Dataproc cluster configuration dictionary

Create a dictionary called cluster_config with these exact entries: 'project_id': 'my-gcp-project', 'cluster_name': 'spark-cluster', 'num_workers': 2, and 'master_machine_type': 'n1-standard-4'.

GCP

# Create the cluster_config dictionary with specified keys and values
# Your code here

Hint

Use curly braces to create a dictionary with the exact keys and values.

2

Add cluster region configuration

Add a variable called region and set it to the string 'us-central1'.

GCP

cluster_config = {
    'project_id': 'my-gcp-project',
    'cluster_name': 'spark-cluster',
    'num_workers': 2,
    'master_machine_type': 'n1-standard-4'
}
# Define the region variable
# Your code here

Hint

Assign the string 'us-central1' to the variable named region.

3

Write Spark job submission code

Write a dictionary called job_config with keys 'cluster_name' and 'main_jar_file_uri'. Set 'cluster_name' to cluster_config['cluster_name'] and 'main_jar_file_uri' to 'gs://my-bucket/spark-job.jar'.

GCP

cluster_config = {
    'project_id': 'my-gcp-project',
    'cluster_name': 'spark-cluster',
    'num_workers': 2,
    'master_machine_type': 'n1-standard-4'
}
region = 'us-central1'
# Create job_config dictionary with cluster_name and main_jar_file_uri
# Your code here

Hint

Use the cluster name from cluster_config and set the jar file URI as shown.

4

Complete Dataproc cluster creation command

Write a command string called create_cluster_cmd that uses gcloud dataproc clusters create with cluster_config['cluster_name'], --region set to region, --num-workers set to cluster_config['num_workers'], and --master-machine-type set to cluster_config['master_machine_type'].

GCP

cluster_config = {
    'project_id': 'my-gcp-project',
    'cluster_name': 'spark-cluster',
    'num_workers': 2,
    'master_machine_type': 'n1-standard-4'
}
region = 'us-central1'
job_config = {
    'cluster_name': cluster_config['cluster_name'],
    'main_jar_file_uri': 'gs://my-bucket/spark-job.jar'
}
# Create the create_cluster_cmd string with gcloud dataproc clusters create command
# Your code here

Hint

Use an f-string to build the command with the exact parameters from cluster_config and region.

Practice

1. What is the main purpose of Google Cloud Dataproc when working with Spark and Hadoop?

easy

A. To manage and simplify running Spark and Hadoop clusters

B. To replace Spark and Hadoop with a new technology

C. To store data permanently like a database

D. To create virtual machines for web hosting

Solution

1. Step 1: Understand Dataproc's role

   Dataproc is a managed service that helps run Spark and Hadoop without manual setup.

2. Step 2: Compare options

   The other options describe replacing Spark and Hadoop, storing data permanently like a database, or creating VMs for web hosting, none of which is Dataproc's main purpose.

3. Final Answer:

   To manage and simplify running Spark and Hadoop clusters -> Option A

4. Quick Check:

   Dataproc manages Spark/Hadoop clusters = A [OK]

Hint: Dataproc manages clusters, not replaces or stores data [OK]

Common Mistakes:

• Thinking Dataproc replaces Spark/Hadoop
• Confusing Dataproc with storage services
• Assuming Dataproc creates VMs for web hosting

2. Which of the following is the correct gcloud command to create a Dataproc cluster named my-cluster in the us-central1 region?

easy

A. gcloud dataproc create cluster my-cluster --region us-central1

B. gcloud dataproc cluster create my-cluster --zone us-central1

C. gcloud dataproc clusters new my-cluster region=us-central1

D. gcloud dataproc clusters create my-cluster --region=us-central1

Solution

1. Step 1: Recall correct gcloud syntax

   The correct command uses 'clusters create' followed by the cluster name and '--region=' flag.

2. Step 2: Check each option

   'gcloud dataproc clusters create my-cluster --region=us-central1' matches the correct syntax. The other options have incorrect order, flags, or keywords.

3. Final Answer:

   gcloud dataproc clusters create my-cluster --region=us-central1 -> Option D

4. Quick Check:

   Correct gcloud cluster create syntax = B [OK]

Hint: Use 'clusters create' and '--region=' flag for cluster creation [OK]

Common Mistakes:

• Using 'create cluster' instead of 'clusters create'
• Missing equal sign in '--region='
• Confusing zone and region flags

3. Given the following command, what will be the result?

gcloud dataproc clusters create test-cluster --region=us-east1 --num-workers=2 --worker-machine-type=n1-standard-2

medium

A. Creates a cluster but in the default region ignoring '--region' flag

B. Creates a cluster named 'test-cluster' with 2 worker nodes of type n1-standard-2 in us-east1

C. Fails because '--num-workers' is not a valid flag

D. Creates a cluster with default worker count and machine type ignoring specified flags

Solution

1. Step 1: Analyze command flags

   The command specifies cluster name, region, number of workers, and worker machine type correctly.

2. Step 2: Understand Dataproc behavior

   Dataproc creates the cluster with given parameters if flags are valid and syntax is correct.

3. Final Answer:

   Creates a cluster named 'test-cluster' with 2 worker nodes of type n1-standard-2 in us-east1 -> Option B

4. Quick Check:

   Flags set cluster size and type correctly = D [OK]

Hint: Flags set cluster size and type; valid flags create cluster as specified [OK]

Common Mistakes:

• Assuming '--num-workers' is invalid
• Ignoring region flag effects
• Thinking default values override flags

4. You run this command to create a Dataproc cluster but get an error:

gcloud dataproc clusters create mycluster --num-worker=3 --region=us-west1

What is the likely cause of the error?

medium

A. Cluster name 'mycluster' is invalid because it has no hyphen

B. The region 'us-west1' is not supported by Dataproc

C. The flag '--num-worker' is incorrect; it should be '--num-workers'

D. Missing machine type flag causes the error

Solution

1. Step 1: Check flag correctness

   The correct flag for worker count is '--num-workers' (plural), not '--num-worker'.

2. Step 2: Validate other inputs

   Region 'us-west1' is valid, cluster name format is acceptable, and machine type is optional with defaults.

3. Final Answer:

   The flag '--num-worker' is incorrect; it should be '--num-workers' -> Option C

4. Quick Check:

   Correct flag spelling fixes error = C [OK]

Hint: Check plural form of flags like '--num-workers' [OK]

Common Mistakes:

• Using singular '--num-worker' instead of plural
• Assuming region is invalid without checking
• Thinking machine type is mandatory

5. You want to run a Spark job on a Dataproc cluster that automatically scales worker nodes between 2 and 5 based on workload. Which feature should you enable when creating the cluster?

hard

A. Enable autoscaling policy and attach it to the cluster

B. Set '--num-workers=5' and manually delete nodes when idle

C. Use '--max-workers=5' without autoscaling policy

D. Create multiple clusters with different sizes and switch between them

Solution

1. Step 1: Understand autoscaling in Dataproc

   Dataproc supports autoscaling policies to adjust worker nodes automatically within set limits.

2. Step 2: Evaluate options

   Enable autoscaling policy and attach it to the cluster correctly enables autoscaling with a policy. The other options do not provide automatic scaling: they either use fixed sizes, incomplete flags without policy, or require manual switching between clusters.

3. Final Answer:

   Enable autoscaling policy and attach it to the cluster -> Option A

4. Quick Check:

   Autoscaling policy enables dynamic scaling = A [OK]

Hint: Use autoscaling policies for automatic worker scaling [OK]

Common Mistakes:

• Setting fixed worker count without autoscaling
• Ignoring autoscaling policies
• Creating multiple clusters instead of scaling one