Resource planning and capacity in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is resource planning in Kafka?

Resource planning in Kafka means deciding how many servers, storage, and network capacity you need to handle your data streams smoothly without delays or crashes.

beginner

Why is capacity important in Kafka clusters?

Capacity ensures Kafka can handle the volume of messages and users. If capacity is too low, messages get delayed or lost. Proper capacity keeps Kafka fast and reliable.

intermediate

What role do partitions play in Kafka resource planning?

Partitions split topics into smaller parts. More partitions mean better parallel processing but need more CPU and memory. Planning partitions helps balance load and resource use.

intermediate

How does replication affect Kafka capacity planning?

Replication copies data to multiple brokers for safety. More replicas mean more storage and network use. You must plan capacity to handle this extra load.

intermediate

What is a common method to monitor Kafka cluster capacity?

Using tools like Kafka's JMX metrics or monitoring platforms (e.g., Prometheus) helps track CPU, memory, disk, and network use to adjust resources before problems happen.

What happens if Kafka cluster capacity is too low?

A Kafka runs faster

B Messages may be delayed or lost

C More partitions are created automatically

D Replication increases

If capacity is too low, Kafka cannot process messages quickly, causing delays or loss.

Which Kafka component helps distribute load for better resource use?

A Consumers

B Topics

C Partitions

D Producers

Partitions split topics so multiple servers can handle data in parallel.

How does replication affect resource needs in Kafka?

A It increases storage and network use

B It decreases CPU usage

C It reduces storage needs

D It removes the need for partitions

Replication copies data to multiple brokers, increasing storage and network requirements.

Which tool can help monitor Kafka cluster capacity?

A Git

B Jenkins

C Docker

D Prometheus

Prometheus collects metrics like CPU and memory usage to monitor Kafka.

Why plan the number of partitions in Kafka?

A To balance load and resource use

B To reduce message size

C To increase replication factor

D To avoid using topics

Partitions help spread the workload, so planning their number balances resource use.

Explain how resource planning helps maintain Kafka performance.

Think about what happens if you don't have enough servers or storage.

Describe the impact of replication on Kafka cluster capacity.

Replication is like making backups, but it uses more resources.

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