kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guozhang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5217) Improve Streams internal exception handling
Date Sat, 23 Sep 2017 04:49:05 GMT

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

Guozhang Wang updated KAFKA-5217:

*Reminder to the contributor / reviewer of the PR*: please note that the code deadline for
1.0.0 is less than 2 weeks away (Oct. 4th). Please re-evaluate your JIRA and see if it still
makes sense to be merged into 1.0.0 or it could be pushed out to 1.1.0, or be closed directly
if the JIRA itself is not valid any more, or re-assign yourself as contributor / committer
if you are no longer working on the JIRA.

> 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:
>            Reporter: Matthias J. Sax
>            Assignee: Matthias J. Sax
>             Fix For: 1.0.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

View raw message