[jira] [Commented] (KAFKA-7970) Missing topic causes service shutdown without exception
[ https://issues.apache.org/jira/browse/KAFKA-7970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872926#comment-16872926 ] Ashish Vyas commented on KAFKA-7970: [~guozhang] any ETA for this one? > 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: > " 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)
[jira] [Commented] (KAFKA-8596) Kafka topic pre-creation error message needs to be passed to application as an exception
[ https://issues.apache.org/jira/browse/KAFKA-8596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872806#comment-16872806 ] Ashish Vyas commented on KAFKA-8596: Thanks for looking into this. I do have uncaughtExceptionHandle registered (and have seen some exceptions once in a while after the stream is successfully started) but it doesn't get triggered for this case when the stream can not start because of non-existing topic. I don't have setStateListener registered. I think you can close this, but not as "not a problem", but may be as duplicate of this open issue - https://issues.apache.org/jira/browse/KAFKA-7970 ? > Kafka topic pre-creation error message needs to be passed to application as > an exception > > > Key: KAFKA-8596 > URL: https://issues.apache.org/jira/browse/KAFKA-8596 > Project: Kafka > Issue Type: Improvement > Components: streams >Affects Versions: 2.1.1 >Reporter: Ashish Vyas >Priority: Minor > > If i don't have a topic pre-created, I get an error log that reads "is > unknown yet during rebalance, please make sure they have been pre-created > before starting the Streams application." Ideally I expect an exception here > being thrown that I can catch in my application and decide what I want to do. > > Without this, my app keeps running and actual functionality doesn't work > making it time consuming to debug. I want to stop the application right at > this point. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
