[
https://issues.apache.org/jira/browse/KAFKA-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945349#comment-14945349
]
Jiangjie Qin commented on KAFKA-2391:
-------------------------------------
[~ijuma] The problem of using request timeout for the public API blocking calls
is that request timeout is for exception handling so it is typically very long.
For users who cares about blocking time, they probably don't want to block for
that long. Therefore request timeout is not an ideal candidate for blocking
timeout. That is why we have max.block.ms for producer. For consumers, I think
we probably want the similar configuration here, so any API call is guaranteed
to return within max.block.ms.
> 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)
