---
id: ab76d240-9640-435c-accd-14c45e2bf1f7
---
# Inadequate Kafka Topic Partitions Incident
---

This incident type refers to a situation where the number of partitions for a Kafka topic is insufficient to handle the incoming data stream. This can lead to low throughput and/or increased write latency. In order to resolve this issue, it may be necessary to increase the number of Kafka topic partitions. Failure to address this issue can lead to degraded performance and potential data loss.

### Parameters
```shell
export BROKER_HOSTNAME="PLACEHOLDER"

export PORT="PLACEHOLDER"

export TOPIC_NAME="PLACEHOLDER"

export NUM_PARTITIONS="PLACEHOLDER"
```

## Debug

### Check the number of partitions for the Kafka topic
```shell
kafka-topics.sh --bootstrap-server ${BROKER_HOSTNAME}:${PORT} --describe --topic ${TOPIC_NAME}
```

### Check the current throughput of the Kafka topic
```shell
kafka-run-class.sh kafka.tools.GetOffsetShell --broker-list ${BROKER_HOSTNAME}:${PORT} --topic ${TOPIC_NAME} --time -1 | awk -F ":" '{sum += $3} END {print sum}'
```

### Check the current write latency of the Kafka topic
```shell
kafka-console-producer.sh --broker-list ${BROKER_HOSTNAME}:${PORT} --topic ${TOPIC_NAME} | kafka-console-consumer.sh --bootstrap-server ${BROKER_HOSTNAME}:${PORT} --topic ${TOPIC_NAME} --consumer-property group.id=test-consumer-group --from-beginning --max-messages 1
```

## Repair

### Increase the number of partitions for the Kafka topic
```shell
kafka-topics.sh --bootstrap-server ${BROKER_HOSTNAME}:${PORT} --alter --topic ${TOPIC_NAME} --partitions ${NUM_PARTITIONS}
```


This incident type refers to a situation where the number of partitions for a Kafka topic is insufficient to handle the incoming data stream. This can lead to low throughput and/or increased write latency. In order to resolve this issue, it may be necessary to increase the number of Kafka topic partitions. Failure to address this issue can lead to degraded performance and potential data loss.


This incident type refers to the detection of an unused topic partition in Kafka Platform, a popular data streaming platform. Unused partitions can increase broker overhead and reduce efficiency, so it is recommended to delete them. The incident is triggered by a test notification or a monitoring query that checks the value of relevant metrics. The incident is resolved once the partition is deleted or confirmed to be intentional.


Unused Topic Partition in Kafka

This incident type refers to a situation where there is an issue with the communication between Kafka brokers due to network partitioning. A network partition is a situation where a network is split into two or more parts, and communication between them is disrupted. This issue can lead to data inconsistency, loss of messages, delayed message delivery, and other related problems. As a result, it is important to quickly detect and resolve these incidents to prevent any downstream impact on the system.


Parameters

This type of incident occurs when the offset of a Kafka topic decreases unexpectedly. In Kafka, an offset is a unique identifier that represents the position of a message within a partition. When the offset decreases, it means that some messages have been lost or deleted, which can cause data inconsistencies or other issues within the system. This incident type is critical for Kafka-based systems as it affects data integrity and can lead to data loss.


Kafka topic offset decreased incident.

This incident type refers to when a Kafka node runs out of storage space to store data. This can cause issues with data processing and storage, potentially leading to data loss and system downtime.


Kafka node insufficient storage check

```shell
export BROKER_HOSTNAME="PLACEHOLDER"

export PORT="PLACEHOLDER"

export TOPIC_NAME="PLACEHOLDER"

export NUM_PARTITIONS="PLACEHOLDER"
```


### Check the number of partitions for the Kafka topic

```shell
kafka-topics.sh --bootstrap-server ${BROKER_HOSTNAME}:${PORT} --describe --topic ${TOPIC_NAME}
```

### Check the current throughput of the Kafka topic

```shell
kafka-run-class.sh kafka.tools.GetOffsetShell --broker-list ${BROKER_HOSTNAME}:${PORT} --topic ${TOPIC_NAME} --time -1 | awk -F ":" '{sum += $3} END {print sum}'
```

### Check the current write latency of the Kafka topic

```shell
kafka-console-producer.sh --broker-list ${BROKER_HOSTNAME}:${PORT} --topic ${TOPIC_NAME} | kafka-console-consumer.sh --bootstrap-server ${BROKER_HOSTNAME}:${PORT} --topic ${TOPIC_NAME} --consumer-property group.id=test-consumer-group --from-beginning --max-messages 1
```


### Increase the number of partitions for the Kafka topic

```shell
kafka-topics.sh --bootstrap-server ${BROKER_HOSTNAME}:${PORT} --alter --topic ${TOPIC_NAME} --partitions ${NUM_PARTITIONS}
```


Inadequate Kafka Topic Partitions Incident

Overview

Parameters

Debug

Check the number of partitions for the Kafka topic

Check the current throughput of the Kafka topic

Check the current write latency of the Kafka topic

Repair

Increase the number of partitions for the Kafka topic

Learn more

Related Runbooks

Unused Topic Partition in Kafka

Network Partitioning Between Kafka Brokers.

Parameters

Kafka topic offset decreased incident.

Support