[jira] [Commented] (KAFKA-2391) Blocking call such as position(), partitionsFor(), committed() and listTopics() should have a timeout

[Ismael Juma (JIRA)]

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

Ismael Juma commented on KAFKA-2391:
------------------------------------

Also note that `NetworkClient.poll` already takes `requestTimeoutMs` into 
account. However, some of the loops check for some condition that won't be 
affected by the request timing out. I also mentioned this example in KAFKA-1894:

{code}
public void awaitMetadataUpdate() {
        int version = this.metadata.requestUpdate();
        do {
            poll(Long.MAX_VALUE);
        } while (this.metadata.version() == version);
    }
{code}

> Blocking call such as position(), partitionsFor(), committed() and 
> listTopics() should have a timeout
> -----------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-2391
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2391
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Jiangjie Qin
>            Assignee: Onur Karaman
>
> The blocking calls should have a timeout from either configuration or 
> parameter. So far we have position(), partitionsFor(), committed() and 
> listTopics().



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