[
https://issues.apache.org/jira/browse/KAFKA-10356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865263#comment-17865263
]
Matthias J. Sax commented on KAFKA-10356:
-----------------------------------------
Talked to a few people, and there was no objection to close this.
> Handle accidental deletion of sink-topics as exceptional failure
> ----------------------------------------------------------------
>
> Key: KAFKA-10356
> URL: https://issues.apache.org/jira/browse/KAFKA-10356
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Guozhang Wang
> Assignee: Bruno Cadonna
> Priority: Major
>
> Today when sink topics are deleted, the producer's send callback would
> eventually return the UnknownTopicOrPartition exception after configured
> max.delivery.ms whose default is 2min if EOS is not enabled (otherwise its
> Integer.MAX_VALUE). Then in Streams implementation the exception would be
> handled by ProductionExceptionHandler which by default would treat it as
> `FAIL` and would cause the thread to die. If it treat it is CONTINUE then it
> would be silently ignored and the sent records are lost silently.
> We should improve this situation in Streams by special-handling
> {{UnknownTopicOrPartition}} exception and trigger a rebalance as well, and
> then in leader we can also check if the sink topic metadata exists, just like
> source topic, and then follow the same logic as in
> https://issues.apache.org/jira/browse/KAFKA-10355.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
