[
https://issues.apache.org/jira/browse/KAFKA-9274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989190#comment-16989190
]
Bill Bejeck commented on KAFKA-9274:
------------------------------------
At the risk of stating the obvious,I think we should have a default number of
`num.timeout.retries`. The `num.timeout.retries` would be a new configuration
(KIP required) that gets applied across the board in a streams application for
all cases where there could be a timeout connecting to the broker.
> Gracefully handle timeout exceptions on Kafka Streams
> -----------------------------------------------------
>
> Key: KAFKA-9274
> URL: https://issues.apache.org/jira/browse/KAFKA-9274
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Boyang Chen
> Priority: Major
>
> Right now streams don't treat timeout exception as retriable in general by
> throwing it to the application level. If not handled by the user, this would
> kill the stream thread unfortunately.
> In fact, timeouts happen mostly due to network issue or server side
> unavailability. Hard failure on client seems to be an over-kill.
> We would like to discuss what's the best practice to handle timeout
> exceptions on Streams. The current state is still brainstorming and
> consolidate all the cases that contain timeout exception within this ticket.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
