You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2015/06/12 03:03:00 UTC

[jira] [Commented] (KAFKA-2266) Client Selector can drop idle connections without notifying NetworkClient

    [ https://issues.apache.org/jira/browse/KAFKA-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582762#comment-14582762 ] 

Jason Gustafson commented on KAFKA-2266:
----------------------------------------

Created reviewboard https://reviews.apache.org/r/35371/diff/
 against branch upstream/trunk

> Client Selector can drop idle connections without notifying NetworkClient
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-2266
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2266
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>         Attachments: KAFKA-2266.patch
>
>
> 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. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)