[KAFKA-2266] Client Selector can drop idle connections without notifying NetworkClient

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.0.0
• Assignee: Jason Gustafson
• Reporter: Jason Gustafson
• Created: 12/Jun/15 00:51
• Updated: 12/Jun/15 17:25
• Resolved: 12/Jun/15 17:25

Description

I've run into this while testing the new consumer. The class org.apache.kafka.common.networ.Selector has code to drop idle connections, but when one is dropped, it is not added to the list of disconnections. This causes inconsistency between Selector and NetworkClient, which depends on this list to update its internal connection states. When a new request is sent to NetworkClient, it still sees the connection as good and forwards it to Selector, which results in an IllegalStateException.