[KAFKA-5301] Improve exception handling on consumer path

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 0.11.0.0
• Component/s: streams
• Assignee: Matthias J. Sax
• Reporter: Eno Thereska
• Created: 22/May/17 09:56
• Updated: 25/Oct/17 23:03
• Resolved: 25/Oct/17 23:03

Description

Used in StreamsThread.java, mostly to .poll() but also to restore data.
Used in StreamsTask.java, mostly to .pause(), .resume()

All exceptions here are currently caught all the way up to the main running loop in a broad catch(Exception e) statement in StreamThread.run().

One main concern on the consumer path is handling deserialization errors that happen before streams has even had a chance to look at the data: https://issues.apache.org/jira/browse/KAFKA-5157

Issue Links

• incorporates: KAFKA-5157 Options for handling corrupt data during deserialization
• is related to: KAFKA-5835 CommitFailedException message is misleading and cause is swallowed
• is related to: KAFKA-6121 Restore and global consumer should not use auto.offset.reset
• is related to: KAFKA-6122 Global Consumer should handle TimeoutException
• links to: GitHub Pull Request #3842