[
https://issues.apache.org/jira/browse/KAFKA-7970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777524#comment-16777524
]
Guozhang Wang commented on KAFKA-7970:
--------------------------------------
As for now, I'd suggest maybe you can grep on the client logs, and trigger the
alert / kill the process when you've seen this error logs: admittedly it is not
ideal, just to workaround it.
> Missing topic causes service shutdown without exception
> -------------------------------------------------------
>
> Key: KAFKA-7970
> URL: https://issues.apache.org/jira/browse/KAFKA-7970
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 2.1.0
> Reporter: Jonny Heavey
> Priority: Minor
>
> When launching a KafkaStreams application that depends on a topic that
> doesn't exist, the streams application correctly logs an error such as:
> "<TOPIC_NAME> is unknown yet during rebalance, please make sure they have
> been pre-created before starting the Streams application."
> The stream is then shutdown, however, no exception is thrown indicating that
> an error has occurred.
> In our circumstances, we run our streams app inside a container. The streams
> service is shutdown, but the process is not exited, meaning that the
> container does not crash (reducing visibility of the issue).
> As no exception is thrown in the missing topic scenario described above, our
> application code has no way to determine that something is wrong that would
> then allow it to terminate the process.
>
> Could the onPartitionsAssigned method in StreamThread.java throw an exception
> when it decides to shutdown the stream (somewhere around line 264)?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
