You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "WooYoung (JIRA)" <ji...@apache.org> on 2019/05/09 02:09:00 UTC

[jira] [Commented] (KAFKA-8311) Better consumer timeout exception handling

    [ https://issues.apache.org/jira/browse/KAFKA-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16836028#comment-16836028 ] 

WooYoung commented on KAFKA-8311:
---------------------------------

Hello [~bchen225242]. I`m a new committer Kafka Project.

I want to analyze this issue and to contribute to this project.

Could you give me an assigner on this issue?

> Better consumer timeout exception handling 
> -------------------------------------------
>
>                 Key: KAFKA-8311
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8311
>             Project: Kafka
>          Issue Type: Improvement
>          Components: consumer, streams
>            Reporter: Boyang Chen
>            Assignee: Boyang Chen
>            Priority: Major
>              Labels: newbie
>
> When stream application crashed due to underlying consumer commit timeout, we have seen following gaps:
> 1. The current timeout exception doesn't provide meaningful tuning instructions. We should augment the error message to let user change `default.api.timeout.ms` in order to tolerate longer reaction time.
> 2. Currently we have 3 different types of consumers on KStream: thread-consumer, global-consumer and restore-consumer. Although we don't plan to explicitly handle this consumer timeout on stream level, we could wrap it with more meaningful message either on consumer or stream level to let user be aware which consumer is having trouble.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)