Description
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.
Attachments
Issue Links
- Is contained by
-
KAFKA-9274 Gracefully handle timeout exceptions on Kafka Streams
-
- Resolved
-