flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4382) Buffer rpc calls until RpcEndpoint is properly started
Date Fri, 12 Aug 2016 08:13:20 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418505#comment-15418505

ASF GitHub Bot commented on FLINK-4382:

Github user tillrohrmann commented on the issue:

    Dropping is also a solution. I think this will also happen implicitly if the mailbox grows
too big.
    Stashing has the advantage that we try (on a best effort basis) to answer early requests.
That way the rpc calls won't have to time out on the sending side before being retried or
alternative measures are taken. Of course this can happen if the start up takes too long on
the server side. Thus, I would imagine that this approach is a little bit more responsive
wrt early rpcs.
    So I don't think that stashing actually hurts.

> Buffer rpc calls until RpcEndpoint is properly started
> ------------------------------------------------------
>                 Key: FLINK-4382
>                 URL: https://issues.apache.org/jira/browse/FLINK-4382
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Distributed Coordination
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
> When creating a {{RpcEndpoint}} it starts a rpc server. The server should wait to dispatch
incoming rpc calls until the {{RpcEndpoint}} signals that it's ready.

This message was sent by Atlassian JIRA

View raw message