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 2019/10/11 09:34:00 UTC

[jira] [Closed] (FLINK-6523) Improve lifecycle management of created BlobCaches in TaskManagerLogHandler and JobClient

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

Till Rohrmann closed FLINK-6523.
--------------------------------
    Resolution: Won't Do

No longer valid.

> Improve lifecycle management of created BlobCaches in TaskManagerLogHandler and JobClient
> -----------------------------------------------------------------------------------------
>
>                 Key: FLINK-6523
>                 URL: https://issues.apache.org/jira/browse/FLINK-6523
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.3.0, 1.4.0
>            Reporter: Till Rohrmann
>            Priority: Major
>
> Some components like the {{JobClient#retrieveClassLoader}} and {{TaskManagerLogHandler}} create {{BlobCaches}} to retrieve data from the {{BlobServer}}. These instances are created in a local context and their lifecycle is not properly managed. The cleanup/closing solely relies on the fact that their storage directory will be cleaned up eventually by a registered shutdown hook.
> I think it would be better to properly implement a lifecycle management for these components and close them at an appropriate location in the code. E.g. one could pass in a shared {{BlobCache}} which is closed once the JobClient action is over.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)