[
https://issues.apache.org/jira/browse/KAFKA-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-8311.
------------------------------------
Resolution: Duplicate
Closing this ticket – KIP-572 / KAFKA-9274 does subsume it.
> 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
(v8.3.4#803005)
