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 2018/12/12 18:52:00 UTC

[jira] [Resolved] (KAFKA-7712) Handle exceptions from immediately connected channels in Selector

     [ https://issues.apache.org/jira/browse/KAFKA-7712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson resolved KAFKA-7712.
------------------------------------
    Resolution: Fixed

> Handle exceptions from immediately connected channels in Selector
> -----------------------------------------------------------------
>
>                 Key: KAFKA-7712
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7712
>             Project: Kafka
>          Issue Type: Bug
>          Components: network
>            Reporter: Rajini Sivaram
>            Assignee: Rajini Sivaram
>            Priority: Major
>             Fix For: 2.2.0
>
>
> We try to handle all possible exceptions in Selector to ensure that channels are always closed and their states kept consistent. For immediately connected channels, we should ensure that any exception during connection results in the channel being closed properly and removed from all maps. This is a very unlikely scenario, but we do already handle the exception. We should clean up properly in the catch block.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)