flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-4853) Clean up JobManager registration at the ResourceManager
Date Sun, 23 Oct 2016 09:20:58 GMT

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

Till Rohrmann closed FLINK-4853.
    Resolution: Fixed

Fixed via 0e965ae3e00454575a8920fce7b97842fdb9e3a9

> Clean up JobManager registration at the ResourceManager
> -------------------------------------------------------
>                 Key: FLINK-4853
>                 URL: https://issues.apache.org/jira/browse/FLINK-4853
>             Project: Flink
>          Issue Type: Sub-task
>          Components: ResourceManager
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
> The current {{JobManager}} registration at the {{ResourceManager}} blocks threads in
the {{RpcService.execute}} pool. This is not ideal and can be avoided by not waiting on a
{{Future}} in this call.
> I propose to encapsulate the leader id retrieval operation in a distinct service so that
it can be separated from the {{ResourceManager}}. This will reduce the complexity of the {{ResourceManager}}
and make the individual components easier to test.

This message was sent by Atlassian JIRA

View raw message