What causes InternalTopicsAlreadySetupException?

An explicit `KafkaStreams#init(...)` call (KIP-698) finds that every internal topic for the application (repartition + changelog topics) already exists on the brokers, so init reports there is nothing to set up. Re-running broker-side state initialization for an application that was already initialized (or whose internal topics were created on a previous run / by a previous instance). Init is invoked with parameters that expect to create topics, but the topics from a prior deployment of the same `application.id` are still present. Two startup paths both try to explicitly initialize the same application.id; the second sees the first's topics already in place.

How do I fix InternalTopicsAlreadySetupException?

Treat InternalTopicsAlreadySetupException from `init()` as a benign 'already done' signal — proceed to `start()` rather than failing the boot. If you genuinely want a clean slate, run the application reset tool to delete internal topics first: `kafka-streams-application-reset.sh --application-id --bootstrap-servers ` (dry-run first), then re-init. Make init idempotent in your bootstrap code: catch InternalTopicsAlreadySetupException and continue, since it only means the broker-side state is in place. Coordinate initialization to a single owner (one job/leader) so multiple instances don't both attempt explicit setup of the same application.id.

Is InternalTopicsAlreadySetupException retriable?

No — InternalTopicsAlreadySetupException is not retriable. Retrying the same call will not help; the underlying cause must be fixed first.

Kafka Exception `InternalTopicsAlreadySetupException`

org.apache.kafka.streams.errors.InternalTopicsAlreadySetupException

Non-retriable Streams

InternalTopicsAlreadySetupException is a Kafka client-side exception (org.apache.kafka.streams.errors.InternalTopicsAlreadySetupException).

Common Causes

An explicit `KafkaStreams#init(...)` call (KIP-698) finds that every internal topic for the application (repartition + changelog topics) already exists on the brokers, so init reports there is nothing to set up.
Re-running broker-side state initialization for an application that was already initialized (or whose internal topics were created on a previous run / by a previous instance).
Init is invoked with parameters that expect to create topics, but the topics from a prior deployment of the same `application.id` are still present.
Two startup paths both try to explicitly initialize the same application.id; the second sees the first's topics already in place.

Solutions

Treat InternalTopicsAlreadySetupException from `init()` as a benign 'already done' signal — proceed to `start()` rather than failing the boot.
If you genuinely want a clean slate, run the application reset tool to delete internal topics first: `kafka-streams-application-reset.sh --application-id <id> --bootstrap-servers <hosts>` (dry-run first), then re-init.
Make init idempotent in your bootstrap code: catch InternalTopicsAlreadySetupException and continue, since it only means the broker-side state is in place.
Coordinate initialization to a single owner (one job/leader) so multiple instances don't both attempt explicit setup of the same application.id.

Example Stack Trace

org.apache.kafka.streams.errors.InternalTopicsAlreadySetupException: All internal topics for the Kafka Streams application already exist on the brokers.
	at org.apache.kafka.streams.KafkaStreams.init(KafkaStreams.java:1402)
	at com.example.streams.App.bootstrap(App.java:71)
	at com.example.streams.App.main(App.java:42)

Diagnostic Commands

kafka-topics.sh --bootstrap-server localhost:9092 --list | grep '^<application.id>-'   # internal topics created by this app

kafka-streams-application-reset.sh --application-id <id> --bootstrap-servers localhost:9092 --dry-run   # preview which internal topics would be deleted

Hitting InternalTopicsAlreadySetupException in production? Conduktor Console gives you real-time visibility into clients, consumer groups, and broker health. Browse every Kafka exception or protocol error code.

Kafka Exception InternalTopicsAlreadySetupException

Common Causes

Solutions

Example Stack Trace

Diagnostic Commands

Related

Kafka Exception `InternalTopicsAlreadySetupException`