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

Posted to dev@kafka.apache.org by "Magnus Edenhill (JIRA)" <ji...@apache.org> on 2016/04/12 09:48:25 UTC

[jira] [Commented] (KAFKA-3547) Broker does not disconnect client on unknown request

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

Magnus Edenhill commented on KAFKA-3547:
----------------------------------------

Fixed in
https://github.com/apache/kafka/commit/bb643f83a95e9ebb3a9f8331fe9998c8722c07d4#diff-d0332a0ff31df50afce3809d90505b25R80

> Broker does not disconnect client on unknown request
> ----------------------------------------------------
>
>                 Key: KAFKA-3547
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3547
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.9.0.0, 0.9.0.1
>            Reporter: Magnus Edenhill
>            Priority: Critical
>             Fix For: 0.10.0.0
>
>
> A regression in 0.9.0 causes the broker to not close a client connection when receiving an unsupported request.
> Two effects of this are:
>  - the client is not informed that the request was not supported (even though a closed connection is a blunt indication it is infact some indication), the request will (hopefully) just time out on the client after some time, stalling sub-sequent operations.
>  - the broker leaks the connection until the connection reaper brings it down or the client closes the connection



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