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 2017/12/06 08:34:00 UTC
[jira] [Closed] (FLINK-6528) Refactor BlobLibraryCacheManager <=>
BlobServer/Cache <=> BlobStore hierarchy
[ https://issues.apache.org/jira/browse/FLINK-6528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-6528.
--------------------------------
Resolution: Resolved
Fix Version/s: 1.4.0
> Refactor BlobLibraryCacheManager <=> BlobServer/Cache <=> BlobStore hierarchy
> -----------------------------------------------------------------------------
>
> Key: FLINK-6528
> URL: https://issues.apache.org/jira/browse/FLINK-6528
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Till Rohrmann
> Fix For: 1.4.0
>
>
> Currently, the {{BlobLibraryCacheManager}} is responsible for keeping reference counts (amongst others) for files stored in the {{BlobServer}}. Additionally it has a periodic timer task which deletes files from the {{BlobServer}} if the reference count is {{0}}.
> The {{BlobServer}} is responsible for storing files locally (on the {{JobManager}}). Moreover, it has a {{BlobStore}} reference which it uses to store files persistently for HA.
> I think it is a wrong separation of concerns that the {{BlobLibraryCacheManager}} is responsible for reference counting. Instead I would propose to move this functionality to the {{BlobServer}} and {{BlobCache}}, respectively. That way, the {{BlobLibraryCacheManager}} is only responsible for keeping track of blobs relevant for a given job and its user code class loader.
> Additionally, we could think about merging the {{BlobServer}}/{{BlobCache}} and the {{BlobStore}} functionality by having a {{FileSystemBlobServer}}/{{FileSystemBlobCache}} which will be configured in the HA case with a DFS path.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)