kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-3547) Broker does not disconnect client on unknown request
Date Tue, 12 Apr 2016 15:19:25 GMT

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

Ismael Juma resolved KAFKA-3547.
--------------------------------
    Resolution: Fixed
      Assignee: Grant Henke

And this is the relevant commit for trunk: https://github.com/apache/kafka/commit/d7fc7cf6154592b7fea494a092e42ad9d45b98a0

> 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
>            Assignee: Grant Henke
>            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)

Mime
View raw message