You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2014/02/01 20:48:09 UTC

[jira] [Updated] (KAFKA-1147) Consumer socket timeout should be greater than fetch max wait

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

Neha Narkhede updated KAFKA-1147:
---------------------------------

    Fix Version/s:     (was: 0.8.1)
                   0.8.2
                   0.9.0

> Consumer socket timeout should be greater than fetch max wait
> -------------------------------------------------------------
>
>                 Key: KAFKA-1147
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1147
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.0, 0.8.1
>            Reporter: Joel Koshy
>            Assignee: Guozhang Wang
>             Fix For: 0.9.0, 0.8.2
>
>         Attachments: KAFKA-1147.patch, KAFKA-1147_2013-12-07_18:22:18.patch, KAFKA-1147_2013-12-09_09:14:24.patch, KAFKA-1147_2013-12-10_14:31:46.patch
>
>
> From the mailing list:
> The consumer-config documentation states that "The actual timeout set
> will be max.fetch.wait + socket.timeout.ms." - however, that change
> seems to have been lost in the code a while ago - we should either fix the doc or re-introduce the addition.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)