[KAFKA-17519] Define and validate correctness of Consumer.close() and its timeout when thread is interrupted

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.9.0
• Fix Version/s: 4.0.0
• Component/s: clients, consumer
• Labels: consumer-threading-refactor kip-848-client-support
• Assignee: Kirk True
• Reporter: Kirk True
• Created: 11/Sep/24 00:41
• Updated: 15/Nov/24 01:44
• Resolved: 15/Nov/24 01:44

Description

The repercussions of a thread's interrupt status on Consumer.close() and its timeout is not well defined. It appears that the ClassicKafkaConsumer will continue to attempt to close all its resources even if an interrupt was triggered prior to—or during—the call to close() though it effectively ignores the user's supplied timeout since each call to NetworkClient.poll() will throw an InterruptException after first making an attempt to poll the socket.

The task here is to review the existing code, verify the behavior with some unit/integration tests, and document it. Furthermore, once the intended behavior has been confirmed, the AsyncKafkaConsumer should be updated to behave likewise.

Issue Links

• is fixed by: KAFKA-16985 Ensure consumer attempts to send leave request on close even if interrupted
• is related to: KAFKA-16985 Ensure consumer attempts to send leave request on close even if interrupted
• is related to: KAFKA-17518 AsyncKafkaConsumer cannot reliably leave group when closed with small timeout