You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2017/10/25 23:04:00 UTC
[jira] [Resolved] (KAFKA-5301) Improve exception handling on
consumer path
[ https://issues.apache.org/jira/browse/KAFKA-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias J. Sax resolved KAFKA-5301.
------------------------------------
Resolution: Duplicate
This issue is contained by KAFKA-6121 and KAFKA-6122, thus I am closing this one.
> Improve exception handling on consumer path
> -------------------------------------------
>
> Key: KAFKA-5301
> URL: https://issues.apache.org/jira/browse/KAFKA-5301
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Affects Versions: 0.11.0.0
> Reporter: Eno Thereska
> Assignee: Matthias J. Sax
>
> Used in StreamsThread.java, mostly to .poll() but also to restore data.
> Used in StreamsTask.java, mostly to .pause(), .resume()
> All exceptions here are currently caught all the way up to the main running loop in a broad catch(Exception e) statement in StreamThread.run().
> One main concern on the consumer path is handling deserialization errors that happen before streams has even had a chance to look at the data: https://issues.apache.org/jira/browse/KAFKA-5157
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)