Batch vs real-time ingestion in Hadoop - Performance Comparison

Time Complexity: Batch vs real-time ingestion

O(n)

Understanding Time Complexity

We want to understand how the time to process data changes when using batch or real-time ingestion in Hadoop.

How does the way data is handled affect the work done as data size grows?

Scenario Under Consideration

Analyze the time complexity of the following Hadoop batch ingestion job.

// Batch ingestion example
Job job = Job.getInstance(conf, "BatchIngestion");
job.setInputFormatClass(TextInputFormat.class);
TextInputFormat.addInputPath(job, new Path(inputPath));
job.setMapperClass(MyMapper.class);
job.setReducerClass(MyReducer.class);
job.setOutputFormatClass(TextOutputFormat.class);
TextOutputFormat.setOutputPath(job, new Path(outputPath));
job.waitForCompletion(true);

This code runs a batch job that reads all input data at once, processes it, and writes output.

Identify Repeating Operations

Look at what repeats during the batch job.

• Primary operation: Reading and processing each data record once in the mapper and reducer.
• How many times: Once for every record in the input data set.

How Execution Grows With Input

As the input data grows, the job processes more records one by one.

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

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

Final Time Complexity

Time Complexity: O(n)

This means the time to finish the batch job grows in a straight line with the amount of data.

Common Mistake

[X] Wrong: "Real-time ingestion always takes less time than batch ingestion."

[OK] Correct: Real-time ingestion handles data in small pieces continuously, but the total work over time can be similar or more depending on data volume and processing steps.

Interview Connect

Understanding how batch and real-time ingestion scale helps you explain trade-offs clearly and shows you know how data size affects processing time in Hadoop jobs.

Self-Check

"What if we changed the batch job to process data in smaller chunks repeatedly instead of all at once? How would the time complexity change?"

Practice

1. Which statement best describes batch ingestion in Hadoop?

easy

A. It only works with streaming data sources.

B. It processes data instantly as it arrives.

C. It requires real-time user interaction to start.

D. It collects and processes data in groups at scheduled times.

Solution

1. Step 1: Understand batch ingestion concept

   Batch ingestion collects data in chunks or groups rather than continuously.

2. Step 2: Compare with real-time ingestion

   Real-time ingestion processes data immediately, unlike batch which waits for scheduled times.

3. Final Answer:

   It collects and processes data in groups at scheduled times. -> Option D

4. Quick Check:

   Batch ingestion = scheduled group processing [OK]

Hint: Batch = grouped data at set times, not instant [OK]

Common Mistakes:

• Confusing batch with real-time ingestion
• Thinking batch requires instant processing
• Assuming batch needs user interaction

2. Which of the following is the correct syntax to start a real-time ingestion job in Hadoop using Apache Flume?

easy

A. hadoop fs -put data.txt /input

B. flume-ng agent -n agent1 -c conf -f conf/flume.conf

C. hadoop jar batchjob.jar input output

D. flume-ng batch -start agent1

Solution

1. Step 1: Identify real-time ingestion tool syntax

   Apache Flume uses the command flume-ng agent to start an agent for real-time ingestion.

2. Step 2: Check other options for correctness

   Options B and C relate to batch or file operations, and D is not a valid Flume command.

3. Final Answer:

   flume-ng agent -n agent1 -c conf -f conf/flume.conf -> Option B

4. Quick Check:

   Flume agent command = real-time start [OK]

Hint: Flume agent command starts real-time ingestion [OK]

Common Mistakes:

• Using batch job commands for real-time ingestion
• Confusing file upload with ingestion start
• Incorrect Flume command syntax

3. Consider this simplified code snippet for batch ingestion in Hadoop MapReduce:

hadoop jar batchjob.jar input_dir output_dir

What will happen when this command runs?

medium

A. It processes all files in input_dir at once and writes results to output_dir.

B. It continuously processes new files as they arrive in input_dir.

C. It deletes input_dir after processing.

D. It streams data from input_dir to output_dir in real-time.

Solution

1. Step 1: Analyze the batch job command

   The command runs a MapReduce job on all data present in input_dir at the time of execution.

2. Step 2: Understand batch vs real-time behavior

   Batch jobs process data in bulk, not continuously or in real-time.

3. Final Answer:

   It processes all files in input_dir at once and writes results to output_dir. -> Option A

4. Quick Check:

   Batch job = bulk processing [OK]

Hint: Batch job runs once on all current input data [OK]

Common Mistakes:

• Thinking batch jobs run continuously
• Assuming input directory is deleted
• Confusing batch with streaming

4. You wrote this Flume configuration to ingest data in real-time:

agent1.sources = source1
agent1.sinks = sink1
agent1.channels = channel1
agent1.sources.source1.type = exec
agent1.sources.source1.command = tail -F /var/log/syslog
agent1.channels.channel1.type = memory
agent1.sinks.sink1.type = hdfs
agent1.sinks.sink1.hdfs.path = /data/logs/

But no data appears in HDFS. What is the likely error?

medium

A. Flume agent was not started with the correct configuration file.

B. The source command 'tail -F' is incorrect; should be 'tail -f'.

C. The channel is not connected to the sink and source.

D. The sink path '/data/logs/' does not exist in HDFS.

Solution

1. Step 1: Check Flume configuration connections

   Flume requires explicit binding of sources, channels, and sinks. Missing bindings cause no data flow.

2. Step 2: Verify bindings in config

   The config lacks lines like agent1.sources.source1.channels = channel1 and agent1.sinks.sink1.channel = channel1.

3. Final Answer:

   The channel is not connected to the sink and source. -> Option C

4. Quick Check:

   Flume needs source-channel-sink bindings [OK]

Hint: Always bind source, channel, and sink in Flume config [OK]

Common Mistakes:

• Ignoring missing bindings in Flume config
• Assuming wrong tail command causes failure
• Thinking sink path must pre-exist

5. You have a large dataset arriving daily and also need to monitor user activity instantly. Which ingestion strategy should you use in Hadoop for each case?

hard

A. Use batch ingestion for daily data and real-time ingestion for user activity.

B. Use real-time ingestion for both daily data and user activity.

C. Use batch ingestion for user activity and real-time ingestion for daily data.

D. Use batch ingestion only for both cases.

Solution

1. Step 1: Analyze data arrival and processing needs

   Large daily data fits batch ingestion since it processes data in groups periodically.

2. Step 2: Consider immediacy of user activity monitoring

   User activity requires instant processing, so real-time ingestion is suitable.

3. Final Answer:

   Use batch ingestion for daily data and real-time ingestion for user activity. -> Option A

4. Quick Check:

   Batch = large periodic, Real-time = instant [OK]

Hint: Batch for big sets, real-time for instant needs [OK]

Common Mistakes:

• Mixing batch and real-time roles
• Using real-time for large daily data unnecessarily
• Ignoring immediacy of user activity data