Description
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 ticket is backed by KIP-572: https://cwiki.apache.org/confluence/display/KAFKA/KIP-572%3A+Improve+timeouts+and+retries+in+Kafka+Streams
Attachments
Issue Links
- causes
-
KAFKA-12951 Infinite loop while restoring a GlobalKTable
- Resolved
- contains
-
KAFKA-9270 KafkaStream crash on offset commit failure
- Resolved
-
KAFKA-8311 Better consumer timeout exception handling
- Resolved
- incorporates
-
KAFKA-7932 Streams needs to handle new Producer exceptions
- Resolved
- is related to
-
KAFKA-8858 Kafka Streams - Failed to Rebalance Error and stream consumer stuck for some reason
- Resolved
- relates to
-
KAFKA-8803 Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId
- Resolved
- links to