Description
Today when source topics are accidently deleted (either before the Streams app is started or while app is already running), the consumer group leader would notice from the metadata refresh that this topic is missing, and then will re-trigger the rebalance. During the rebalance the leader then would encode a `INCOMPLETE_SOURCE_TOPIC_METADATA` in the assignment to let all threads to shutdown upon getting the error.
However, this shutdown process is a graceful shutdown and would only print an ERROR log entry "Received error code INCOMPLETE_SOURCE_TOPIC_METADATA - shutdown". That means users would not be programmatically notified when this happens. We should handle it not as a graceful shutdown but as a Shutdown a Kafka Streams Application error case which would trigger user's error handler with appropriate error reported.
Attachments
Issue Links
- duplicates
-
KAFKA-7970 Missing topic causes service shutdown without exception
-
- Resolved
-
- relates to
-
KAFKA-10357 Handle accidental deletion of repartition-topics as exceptional failure
-
- Open
-
-
-
- Resolved
-
- links to