[
https://issues.apache.org/jira/browse/KAFKA-9274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032577#comment-17032577
]
ASF GitHub Bot commented on KAFKA-9274:
---------------------------------------
guozhangwang commented on pull request #8060: KAFKA-9274: Gracefully handle
timeout exception [WIP]
URL: https://github.com/apache/kafka/pull/8060
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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)
