Google Dataproc overview in Apache Spark - Step-by-Step Execution

Concept Flow - Google Dataproc overview

User submits job to Dataproc

↓

Dataproc creates a cluster

↓

Cluster runs Apache Spark job

↓

Job processes data on cluster nodes

↓

Results returned to user

↓

User deletes cluster to save cost

This flow shows how a user submits a Spark job to Google Dataproc, which creates a cluster, runs the job, processes data, returns results, and then the cluster is deleted.

Execution Sample

Apache Spark

from pyspark.sql import SparkSession
spark = SparkSession.builder.appName('example').getOrCreate()
data = spark.range(5)
data.show()

This code creates a Spark session on Dataproc, generates a simple dataset of numbers 0 to 4, and shows it.

Execution Table

Step	Action	Spark Session State	Data Created	Output
1	Create SparkSession	Active	None	None
2	Generate range data 0-4	Active	[0,1,2,3,4]	None
3	Show data	Active	[0,1,2,3,4]	0 1 2 3 4
4	Job complete	Active	[0,1,2,3,4]	Displayed data
5	Stop SparkSession	Stopped	[0,1,2,3,4]	None

💡 Spark job finishes and session stops or cluster is deleted to save cost.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
spark	None	SparkSession Active	SparkSession Active	SparkSession Active	Stopped
data	None	None	[0,1,2,3,4]	[0,1,2,3,4]	[0,1,2,3,4]

Key Moments - 2 Insights

Why do we need to create a SparkSession before running any job?

The SparkSession is the entry point to use Spark. Without it, you cannot create or run Spark jobs. See execution_table step 1 where SparkSession is created first.

What happens if we do not stop the SparkSession or delete the cluster?

The cluster and SparkSession keep running and cost money. It's important to stop or delete them after the job finishes, as shown in execution_table step 5.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what data is shown?

A Numbers 0 to 4

B Empty dataset

C Numbers 1 to 5

D Error message

💡 Hint

Check the 'Output' column at step 3 in execution_table.

At which step does the SparkSession become active?

A Step 2

B Step 1

C Step 3

D Step 5

💡 Hint

Look at the 'Spark Session State' column in execution_table.

If the cluster is not deleted after job completion, what is the likely impact?

A No impact, it stops automatically

B Job will rerun automatically

C Costs continue to accumulate

D Data will be lost

💡 Hint

Refer to key_moments about stopping SparkSession or deleting cluster.

Concept Snapshot

Google Dataproc runs Apache Spark jobs on managed clusters.
User submits job -> Dataproc creates cluster -> Spark job runs -> Results returned.
Stop or delete cluster after job to save cost.
SparkSession is needed to run Spark code.
Simple data like ranges can be created and shown easily.

Full Transcript

Google Dataproc is a managed service to run Apache Spark jobs on clusters in the cloud. The user submits a Spark job, Dataproc creates a cluster, runs the job, processes data, and returns results. The SparkSession is the main interface to run Spark code. After the job finishes, stopping the SparkSession or deleting the cluster is important to avoid extra costs. In the example, a SparkSession is created, a simple dataset of numbers 0 to 4 is generated, and the data is displayed. This shows the basic flow of running Spark jobs on Dataproc.

Practice

1. What is the main purpose of Google Dataproc in data processing?

easy

A. To run Spark and Hadoop jobs easily in the cloud

B. To store large amounts of data permanently

C. To create visual dashboards for data

D. To write SQL queries on local machines

Solution

1. Step 1: Understand Google Dataproc's role

   Google Dataproc is designed to simplify running big data jobs like Spark and Hadoop in the cloud.

2. Step 2: Compare options with this role

   Only To run Spark and Hadoop jobs easily in the cloud describes running Spark and Hadoop jobs easily in the cloud, which matches Dataproc's main purpose.

3. Final Answer:

   To run Spark and Hadoop jobs easily in the cloud -> Option A

4. Quick Check:

   Dataproc = Run Spark/Hadoop jobs [OK]

Hint: Remember Dataproc runs Spark/Hadoop jobs in cloud [OK]

Common Mistakes:

• Confusing Dataproc with storage services
• Thinking Dataproc creates dashboards
• Assuming Dataproc runs queries locally

2. Which of the following is the correct way to create a cluster in Google Dataproc using gcloud CLI?

easy

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

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

C. gcloud create dataproc cluster my-cluster --region=us-central1

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

Solution

1. Step 1: Recall correct gcloud command syntax

   The correct command to create a Dataproc cluster is 'gcloud dataproc clusters create' followed by the cluster name and region.

2. Step 2: Match options with correct syntax

   gcloud dataproc clusters create my-cluster --region=us-central1 matches the correct syntax exactly. Other options have wrong order or missing keywords.

3. Final Answer:

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

4. Quick Check:

   Correct gcloud create cluster syntax = gcloud dataproc clusters create my-cluster --region=us-central1 [OK]

Hint: Use 'gcloud dataproc clusters create' to make clusters [OK]

Common Mistakes:

• Mixing order of commands
• Using 'create cluster' instead of 'clusters create'
• Confusing region and zone flags

3. Given the following code snippet to submit a Spark job on Dataproc, what will be the output if the cluster name is incorrect?

gcloud dataproc jobs submit spark --cluster wrong-cluster --region us-central1 --class org.apache.spark.examples.SparkPi --jars file:///usr/lib/spark/examples/jars/spark-examples.jar -- 1000

medium

A. Job runs successfully and outputs Pi estimation

B. Error: Cluster 'wrong-cluster' not found

C. Job runs but with default cluster

D. Syntax error in command

Solution

1. Step 1: Understand job submission with cluster name

   The command submits a Spark job to a specific cluster named 'wrong-cluster'. If this cluster does not exist, the job cannot run.

2. Step 2: Predict behavior when cluster name is wrong

   Dataproc will return an error stating the cluster is not found, so the job will not run.

3. Final Answer:

   Error: Cluster 'wrong-cluster' not found -> Option B

4. Quick Check:

   Wrong cluster name = Cluster not found error [OK]

Hint: Check cluster name carefully before submitting jobs [OK]

Common Mistakes:

• Assuming job runs on default cluster
• Thinking command syntax is wrong
• Ignoring error messages about cluster

4. You tried to delete a Dataproc cluster using the command:

gcloud dataproc clusters delete my-cluster --region us-central1

But you get an error saying the cluster is busy. What is the likely cause and how to fix it?

medium

A. Region flag is incorrect; remove the region flag

B. You need to restart the cluster before deleting

C. Cluster name is misspelled; rename the cluster

D. Cluster is running jobs; wait for jobs to finish or cancel them

Solution

1. Step 1: Understand why cluster deletion can fail

   If a cluster is busy running jobs, Dataproc prevents deletion to avoid interrupting work.

2. Step 2: Identify correct fix

   Wait for running jobs to finish or cancel them before deleting the cluster. Other options do not address the busy state.

3. Final Answer:

   Cluster is running jobs; wait for jobs to finish or cancel them -> Option D

4. Quick Check:

   Busy cluster = wait or cancel jobs before delete [OK]

Hint: Stop running jobs before deleting cluster [OK]

Common Mistakes:

• Ignoring running jobs causing busy state
• Removing region flag unnecessarily
• Trying to rename cluster to fix deletion

5. You want to process a large dataset using Spark on Google Dataproc. To save costs, which approach is best?

hard

A. Create multiple clusters for each small job and keep them all running

B. Create a cluster and keep it running 24/7 for all future jobs

C. Create a cluster, run the job, then delete the cluster immediately after

D. Run jobs locally to avoid cloud costs

Solution

1. Step 1: Understand cost management in Dataproc

   Dataproc charges for cluster uptime. Keeping clusters running when not needed increases cost.

2. Step 2: Choose cost-saving approach

   Creating a cluster only when needed, running the job, then deleting it saves money by not paying for idle time.

3. Final Answer:

   Create a cluster, run the job, then delete the cluster immediately after -> Option C

4. Quick Check:

   Delete cluster after job to save cost [OK]

Hint: Delete clusters after jobs to avoid extra charges [OK]

Common Mistakes:

• Leaving clusters running idle
• Running jobs locally ignoring cloud benefits
• Creating many clusters and not deleting them