Resource planning and capacity in Kafka - Step-by-Step Execution

Process Flow - Resource planning and capacity

Estimate workload

↓

Determine resource needs

↓

Check current capacity

↓

Compare needs vs capacity

↓

Allocate

↓

Monitor usage and adjust

↓

Repeat

This flow shows how to estimate workload, check capacity, allocate or scale resources, and monitor continuously.

Execution Sample

Kafka

producer = KafkaProducer(bootstrap_servers='localhost:9092')
partitions = producer.partitions_for('topic')
needed_capacity = calculate_load()
current_capacity = len(partitions)
if needed_capacity > current_capacity:
    scale_up_resources()

This code checks if the needed capacity exceeds current partitions and scales up if needed.

Process Table

Step	Action	Needed Capacity	Current Capacity	Condition	Result
1	Calculate workload	5	N/A	N/A	Needed capacity set to 5
2	Get current partitions	5	3	N/A	Current capacity is 3
3	Compare needed vs current	5	3	5 > 3	True - need to scale up
4	Scale up resources	5	3	N/A	Scaling up to meet capacity
5	Re-check capacity	5	5	5 >= 5	False - capacity sufficient
6	Allocate resources	5	5	N/A	Resources allocated
7	Monitor usage	5	5	N/A	Monitoring ongoing

💡 Capacity meets needed load, no further scaling required

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	Final
needed_capacity	0	5	5	5	5
current_capacity	0	0	3	5	5

Key Moments - 3 Insights

Why do we compare needed_capacity with current_capacity?

We compare them (see execution_table step 3) to decide if we must add more resources or if current ones are enough.

What happens if needed_capacity is less than or equal to current_capacity?

As shown in step 5, no scaling is needed and resources are allocated directly.

Why do we monitor usage after allocation?

Monitoring (step 7) helps catch changes in workload early so we can adjust resources before problems occur.

Visual Quiz - 3 Questions

Look at the execution_table, what is the current_capacity after step 2?

A 5

B 3

C 0

D N/A

💡 Hint

Check the 'current_capacity' column in row for step 2.

At which step does the system decide to scale up resources?

A Step 5

B Step 3

C Step 4

D Step 6

💡 Hint

Look at the 'Result' column where scaling action happens.

If needed_capacity was 2 instead of 5, what would happen at step 3?

A Condition would be false, no scaling needed

B Condition would be true, scaling needed

C Current capacity would increase automatically

D Program would exit immediately

💡 Hint

Compare needed_capacity and current_capacity values in step 3.

Concept Snapshot

Resource planning in Kafka means estimating workload,
checking current partitions (capacity),
comparing needs to capacity,
scaling up if needed,
allocating resources,
and monitoring usage continuously.

Full Transcript

Resource planning and capacity in Kafka involves estimating how much workload the system will have, then checking how many partitions or resources are currently available. If the needed capacity is more than what is available, the system scales up resources to meet demand. Once capacity matches the workload, resources are allocated and usage is monitored to adjust as needed. This process repeats to keep the system balanced and efficient.

Practice

1. What is the main goal of resource planning in Kafka?

easy

A. To reduce the number of topics in Kafka

B. To increase the size of Kafka messages

C. To limit the number of users accessing Kafka

D. To ensure Kafka can handle the expected data load smoothly

Solution

1. Step 1: Understand resource planning purpose

   Resource planning is about preparing Kafka to manage data efficiently without delays or failures.

2. Step 2: Identify the main goal

   The main goal is to handle the expected data load smoothly, avoiding bottlenecks or crashes.

3. Final Answer:

   To ensure Kafka can handle the expected data load smoothly -> Option D

4. Quick Check:

   Resource planning = handle data load smoothly [OK]

Hint: Resource planning means handling data load well [OK]

Common Mistakes:

• Confusing resource planning with limiting users
• Thinking it reduces topics or message sizes
• Ignoring the data load aspect

2. Which of the following is the correct way to increase Kafka capacity?

easy

A. Add more brokers to the Kafka cluster

B. Decrease the number of partitions per topic

C. Reduce the hardware resources of brokers

D. Limit the number of consumers

Solution

1. Step 1: Review capacity factors in Kafka

   Capacity depends on brokers, partitions, and hardware resources.

2. Step 2: Identify correct capacity increase method

   Adding more brokers increases cluster capacity by distributing load.

3. Final Answer:

   Add more brokers to the Kafka cluster -> Option A

4. Quick Check:

   More brokers = more capacity [OK]

Hint: Add brokers to increase capacity [OK]

Common Mistakes:

• Thinking decreasing partitions increases capacity
• Reducing hardware lowers capacity
• Limiting consumers does not increase capacity

3. Given a Kafka cluster with 3 brokers and 6 partitions per topic, what happens if you increase partitions to 12 without adding brokers?

medium

A. The number of consumers must be reduced

B. The cluster automatically adds brokers to handle the load

C. The load per broker increases, possibly causing performance issues

D. Kafka will reject the partition increase request

Solution

1. Step 1: Understand partition increase effect

   Increasing partitions without adding brokers means more load per broker.

2. Step 2: Analyze cluster behavior

   Kafka does not auto-add brokers; load per broker rises, risking performance issues.

3. Final Answer:

   The load per broker increases, possibly causing performance issues -> Option C

4. Quick Check:

   More partitions + same brokers = more load per broker [OK]

Hint: More partitions without brokers = more load per broker [OK]

Common Mistakes:

• Assuming Kafka auto-adds brokers
• Thinking consumers must be reduced
• Believing Kafka rejects partition increase

4. You have a Kafka cluster with 5 brokers but notice high CPU usage on one broker only. What is the likely cause?

medium

A. Uneven partition distribution causing load imbalance

B. All brokers have equal load by design

C. Kafka automatically balances CPU usage evenly

D. The broker hardware is faulty and cannot be fixed

Solution

1. Step 1: Understand load distribution in Kafka

   Partitions are assigned to brokers; uneven distribution causes load imbalance.

2. Step 2: Identify cause of high CPU on one broker

   Uneven partition assignment can overload one broker, causing high CPU usage.

3. Final Answer:

   Uneven partition distribution causing load imbalance -> Option A

4. Quick Check:

   Uneven partitions = uneven CPU load [OK]

Hint: Check partition distribution for load imbalance [OK]

Common Mistakes:

• Assuming Kafka balances CPU automatically
• Blaming hardware without checking partitions
• Thinking all brokers always have equal load

5. You want to plan capacity for a Kafka cluster expected to handle 1 million messages per second. Which combination is best to start with?

hard

A. 5 brokers with 5 partitions each and low memory hardware

B. 10 brokers with 100 partitions each and high-performance SSD storage

C. 2 brokers with 10 partitions each and standard HDD storage

D. 1 broker with 200 partitions and no replication

Solution

1. Step 1: Analyze message load requirements

   1 million messages per second is very high; needs many brokers and partitions.

2. Step 2: Choose hardware and partition setup

   High-performance SSDs and many brokers with many partitions support high throughput and reliability.

3. Final Answer:

   10 brokers with 100 partitions each and high-performance SSD storage -> Option B

4. Quick Check:

   High load needs many brokers, partitions, and fast storage [OK]

Hint: High load needs many brokers, partitions, and SSDs [OK]

Common Mistakes:

• Choosing too few brokers or partitions
• Ignoring storage speed impact
• Not planning for replication and reliability