You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/01/24 10:53:00 UTC

[jira] [Created] (FLINK-8501) Use single BlobCacheService per TaskExecutor

Till Rohrmann created FLINK-8501:
------------------------------------

             Summary: Use single BlobCacheService per TaskExecutor
                 Key: FLINK-8501
                 URL: https://issues.apache.org/jira/browse/FLINK-8501
             Project: Flink
          Issue Type: Improvement
          Components: Distributed Coordination
    Affects Versions: 1.5.0
            Reporter: Till Rohrmann
            Assignee: Till Rohrmann
             Fix For: 1.5.0


Currently, the {{TaskExecutor}} creates a new {{BlobCacheService}} for each new {{JobManagerConnection}}. This is wasteful and, moreover, gives only access to the {{BlobService}} after a connection to a {{JobMaster}} has been established. Due to this, it is not possible to upload the {{TaskExecutor}} logs before a {{TaskExecutor}} is used by a {{JobMaster}}.

 

Since the {{BlobServer}} address is something cluster specific and not {{JobMaster}} specific, I propose to propagate this information when the {{TaskExecutor}} registers at the {{ResourceManager}}. Moreover, I propose to make the {{BlobCacheService}} reusable in case of a {{BlobServer}} address change (e.g. failover) by allowing to change the {{BlobServer}} address.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)