[
https://issues.apache.org/jira/browse/KAFKA-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846356#comment-16846356
]
WooYoung commented on KAFKA-8311:
---------------------------------
[~bchen225242] , I have written merge request message on
[https://github.com/apache/kafka/pull/6792]
However you had suggested me that I need to try to this Jira ticket after
[https://github.com/apache/kafka/pull/6662] was merged first.
I have waited that the ticket was merged, but there is nothing changed.
So I tried that I think this is not appropriate to give merge request about
same Jira ticket.
If this is a problem, plz tell me cancel the ticket of
[https://github.com/apache/kafka/pull/6792].
> 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: WooYoung
> 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)
