[KAFKA-4375] Kafka consumer may swallow some interrupts meant for the calling thread

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.10.1.0
• Fix Version/s: 0.10.2.0
• Component/s: clients
• Assignee: Stig Rohde Døssing
• Reporter: Stig Rohde Døssing
• Created: 03/Nov/16 19:24
• Updated: 09/Dec/16 19:37
• Resolved: 09/Dec/16 19:36

Description

Apache Storm has added a new data source ("spout") based on the Kafka 0.9 consumer. Storm interacts with the consumer by having one thread per spout instance loop calls to poll/commitSync etc. When Storm shuts down, another thread indicates that the looping threads should shut down by interrupting them, and joining them.

If one of the looping threads happen to be interrupted while executing certain sleeps in some consumer methods (commitSync and committed at least), the interrupt can be lost because they contain a call to SystemTime.sleep, which swallows the interrupt.

Is this behavior by design, or can SystemTime be changed to reset the thread interrupt flag when catching an InterruptedException?

I haven't checked the rest of the client code, so it's possible that this is an issue in other parts of the code too.

Issue Links

• is duplicated by: KAFKA-4356 o.a.k.common.utils.SystemTime.sleep() swallows InterruptedException
• links to: GitHub Pull Request #2100