[
https://issues.apache.org/jira/browse/FLINK-8501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354128#comment-16354128
]
ASF GitHub Bot commented on FLINK-8501:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/5350
> 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
> Priority: Major
> Labels: flip-6
> 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)
