kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Onur Karaman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-2391) Blocking call such as position(), partitionsFor(), committed() and listTopics() should have a timeout
Date Wed, 07 Oct 2015 18:01:27 GMT

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

Onur Karaman commented on KAFKA-2391:
-------------------------------------

As brought up earlier, blocking for request.timeout.ms time doesn't seem like the right way
to go:
- if request.timeout.ms < session.timeout.ms, then a user may drop JoinGroupResponses which
can arrive worst case after session.timeout.ms.
- if request.timeout.ms > session.timeout.ms, then a user calling one of these blocking
calls will lose their session and trigger a rebalance.

> 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)

Mime
View raw message