Migration from Hadoop to cloud-native - Time & Space Complexity

Time Complexity: Migration from Hadoop to cloud-native

O(n)

Understanding Time Complexity

When moving data processing from Hadoop to cloud-native systems, it is important to understand how the time to complete tasks changes.

We want to know how the work grows as data size grows during this migration.

Scenario Under Consideration

Analyze the time complexity of the following Hadoop MapReduce job.

// Hadoop MapReduce example
public class WordCount {
  public static class Mapper extends Mapper {
    public void map(LongWritable key, Text value, Context context) {
      for (String word : value.toString().split(" ")) {
        context.write(new Text(word), new IntWritable(1));
      }
    }
  }

  public static class Reducer extends Reducer {
    public void reduce(Text key, Iterable values, Context context) {
      int sum = 0;
      for (IntWritable val : values) {
        sum += val.get();
      }
      context.write(key, new IntWritable(sum));
    }
  }
}

This code counts how many times each word appears in a large text dataset using Hadoop MapReduce.

Identify Repeating Operations

Look at the loops that repeat work:

• Primary operation: The Mapper loops over every word in each input line.
• How many times: Once for every word in the input data.
• Secondary operation: The Reducer loops over all counts for each word to sum them.
• How many times: Once for each occurrence of each word.

How Execution Grows With Input

As the input data size grows, the number of words grows roughly in the same way.

Input Size (n words)	Approx. Operations
10	About 10 word processing steps
100	About 100 word processing steps
1000	About 1000 word processing steps

Pattern observation: The work grows directly with the number of words; doubling words doubles work.

Final Time Complexity

Time Complexity: O(n)

This means the time to process grows in a straight line with the amount of data.

Common Mistake

[X] Wrong: "Migrating to cloud-native will always make processing faster regardless of data size."

[OK] Correct: The time still depends on data size; cloud tools may be faster per unit but the overall growth with data remains linear.

Interview Connect

Understanding how data size affects processing time helps you explain migration benefits clearly and shows you grasp core data engineering concepts.

Self-Check

"What if we changed the Reducer to combine counts before sending data? How would the time complexity change?"

Practice

1. What is the main benefit of migrating Hadoop workloads to cloud-native platforms?

easy

A. Better scalability and easier management

B. Reduced data storage capacity

C. Elimination of all data processing

D. Increased hardware maintenance

Solution

1. Step 1: Understand Hadoop migration goals

   Migration aims to improve how Hadoop workloads scale and are managed.

2. Step 2: Identify benefits of cloud-native platforms

   Cloud platforms offer flexible scaling and easier cluster management compared to on-premises Hadoop.

3. Final Answer:

   Better scalability and easier management -> Option A

4. Quick Check:

   Cloud migration = scalability + management [OK]

Hint: Think why cloud is popular for big data [OK]

Common Mistakes:

• Confusing storage reduction with scalability
• Assuming migration removes data processing
• Thinking hardware maintenance increases

2. Which of the following is the correct syntax to start a Hadoop job on AWS EMR using the AWS CLI?

easy

A. aws emr run-job --id j-2AXXXXXXGAPLF --type Spark --file myapp.jar

B. aws emr start-job --cluster j-2AXXXXXXGAPLF --job Spark --args s3://mybucket/myapp.jar

C. aws emr add-steps --cluster-id j-2AXXXXXXGAPLF --steps Type=Spark,Name="Spark Program",ActionOnFailure=CONTINUE,Args=[--class,org.apache.spark.examples.SparkPi,s3://mybucket/myapp.jar,10]

D. aws emr submit-step --cluster j-2AXXXXXXGAPLF --step Spark --jar myapp.jar

Solution

1. Step 1: Review AWS EMR CLI syntax for adding steps

   The correct command uses aws emr add-steps with detailed step parameters.

2. Step 2: Match syntax with options

   aws emr add-steps --cluster-id j-2AXXXXXXGAPLF --steps Type=Spark,Name="Spark Program",ActionOnFailure=CONTINUE,Args=[--class,org.apache.spark.examples.SparkPi,s3://mybucket/myapp.jar,10] matches the official syntax with cluster ID, step type, name, failure action, and arguments.

3. Final Answer:

   aws emr add-steps --cluster-id j-2AXXXXXXGAPLF --steps Type=Spark,Name="Spark Program",ActionOnFailure=CONTINUE,Args=[--class,org.apache.spark.examples.SparkPi,s3://mybucket/myapp.jar,10] -> Option C

4. Quick Check:

   Use add-steps with detailed args [OK]

Hint: Remember AWS EMR uses add-steps command [OK]

Common Mistakes:

• Using non-existent commands like start-job
• Omitting required step parameters
• Incorrect option names or flags

3. Given the following Python snippet using Google Cloud Dataproc API to submit a Hadoop job, what will be the output if the job completes successfully?

from google.cloud import dataproc_v1
client = dataproc_v1.JobControllerClient()
job = {
  "placement": {"cluster_name": "my-cluster"},
  "hadoop_job": {"main_jar_file_uri": "gs://my-bucket/my-job.jar"}
}
response = client.submit_job(project_id="my-project", region="us-central1", job=job)
print(response.status.state)

medium

A. JobStatus.State.DONE

B. JobStatus.State.ERROR

C. JobStatus.State.RUNNING

D. JobStatus.State.PENDING

Solution

1. Step 1: Understand the job submission and response

   The submit_job method returns a job response with a status field indicating job state.

2. Step 2: Interpret the status.state value after submission

   The submit_job returns immediately with initial state JobStatus.State.PENDING. The print occurs right after submission, before completion, even if the job succeeds later.

3. Final Answer:

   JobStatus.State.PENDING -> Option D

4. Quick Check:

   submit_job initial state = PENDING [OK]

Hint: submit_job returns PENDING immediately [OK]

Common Mistakes:

• Thinking the code waits for DONE on completion
• Confusing initial PENDING with final state
• Assuming RUNNING or ERROR on submission

4. You tried migrating a Hadoop job to AWS EMR but got an error: AccessDeniedException. What is the most likely cause?

medium

A. The EMR cluster is not running

B. The IAM role lacks permissions to access S3 bucket

C. The Hadoop job jar file is corrupted

D. The AWS CLI version is outdated

Solution

1. Step 1: Analyze the error type AccessDeniedException

   This error usually means permission issues, especially with AWS IAM roles.

2. Step 2: Identify common permission problems in EMR migration

   AccessDeniedException often occurs if the EMR cluster's IAM role cannot read the S3 bucket containing job files.

3. Final Answer:

   The IAM role lacks permissions to access S3 bucket -> Option B

4. Quick Check:

   AccessDenied = permission issue [OK]

Hint: AccessDenied usually means permission problem [OK]

Common Mistakes:

• Blaming corrupted jar without checking permissions
• Assuming cluster state causes access errors
• Ignoring IAM role permissions

5. You want to migrate a large Hadoop dataset to a cloud-native platform but want to minimize downtime. Which approach is best?

hard

A. Use incremental data replication with tools like DistCp to sync data continuously

B. Copy all data once during a maintenance window and stop all jobs

C. Manually upload data files via FTP to cloud storage

D. Run Hadoop jobs locally without migration

Solution

1. Step 1: Understand downtime minimization in migration

   Minimizing downtime requires continuous syncing rather than one-time full copy.

2. Step 2: Identify best tool for incremental replication

   DistCp supports incremental copying of Hadoop data to cloud storage, enabling near-zero downtime migration.

3. Final Answer:

   Use incremental data replication with tools like DistCp to sync data continuously -> Option A

4. Quick Check:

   Incremental sync = less downtime [OK]

Hint: Incremental sync tools reduce downtime [OK]

Common Mistakes:

• Doing one-time full copy causing long downtime
• Using manual FTP uploads for big data
• Avoiding migration by running locally