Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
Description
When a TimeoutException is thrown directly in the client side, it doesn't have any stack trace because it inherits "org.apache.kafka.common.errors.ApiException". This makes the user hard to debug timeout issues, because it's hard to know which line in the user codes throwing this TimeoutException.
It would be great that adding a new client side TimeoutException which contains the stack trace.
Attachments
Issue Links
- duplicates
-
KAFKA-7016 Reconsider the "avoid the expensive and useless stack trace for api exceptions" practice
- Open