You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2016/10/18 14:59:59 UTC

[jira] [Created] (FLINK-4853) Clean up JobManager registration at the ResourceManager

Till Rohrmann created FLINK-4853:
------------------------------------

             Summary: 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
(v6.3.4#6332)