[ 
https://issues.apache.org/jira/browse/KAFKA-10355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bruno Cadonna updated KAFKA-10355:
----------------------------------
    Fix Version/s: 2.7.0

> Handle accidental deletion of source-topics as exceptional failure
> ------------------------------------------------------------------
>
>                 Key: KAFKA-10355
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10355
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Guozhang Wang
>            Assignee: Bruno Cadonna
>            Priority: Major
>             Fix For: 2.7.0
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to