[ https://issues.apache.org/jira/browse/KAFKA-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guozhang Wang reopened KAFKA-5217: ---------------------------------- [~enothereska] The parent JIRA is an umbrella story of improving error handling in Streams, while this JIRA itself has a defined sub-task scope on the streams internal exception handling. Have you made a thorough pass over all the call traces to make sure all the issues are already resolved? One example I can tell is that, in {{KeyValueStore.put(k, v)}} function we may throw KafkaException or StreamsException from the {{StoreChangeLogger}} although we do not document in in the javadocs. Though it is debatable that whether we should encourage users to ever try-catch all Exceptions in their cals, I'm afraid there are maybe other cases that we have not thought about yet. > Improve Streams internal exception handling > ------------------------------------------- > > Key: KAFKA-5217 > URL: https://issues.apache.org/jira/browse/KAFKA-5217 > Project: Kafka > Issue Type: Sub-task > Components: streams > Affects Versions: 0.10.2.1 > Reporter: Matthias J. Sax > Assignee: Matthias J. Sax > Fix For: 0.11.1.0 > > > Streams does not handle all exceptions gracefully atm, but tend to throw > exceptions to the user, even if we could handle them internally and recover > automatically. We want to revisit this exception handling to be more > resilient. > For example, for any kind of rebalance exception, we should just log it, and > rejoin the consumer group. -- This message was sent by Atlassian JIRA (v6.4.14#64029)