[
https://issues.apache.org/jira/browse/KAFKA-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16836381#comment-16836381
]
Matthias J. Sax commented on KAFKA-8311:
----------------------------------------
Thanks for you interest [~clearpal7]! I added you to the list of contributors
and assigned the ticket to you. You can now also self-assign tickets.
As Boyang mentioned, you should also subscribe to the dev-mailing list:
[https://kafka.apache.org/contact]
Additionally, please read the wiki:
[https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Code+Changes]
(just as a starting point – there are other pager that provide useful
information to get started).
> 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)
