flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaogang Shi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5925) Clean up extracted RocksDB JNI library
Date Wed, 01 Mar 2017 04:07:45 GMT

    [ https://issues.apache.org/jira/browse/FLINK-5925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889462#comment-15889462
] 

Xiaogang Shi commented on FLINK-5925:
-------------------------------------

+1 for the cleanup mechanism. Each component (e.g. {{TaskManager}}, {{Task}} and {{StateBackend}})
should be given a working directory and it should place all its files in that directory. When
the component exists, we can simply delete the directory to clean unused files.

> Clean up extracted RocksDB JNI library
> --------------------------------------
>
>                 Key: FLINK-5925
>                 URL: https://issues.apache.org/jira/browse/FLINK-5925
>             Project: Flink
>          Issue Type: Bug
>          Components: State Backends, Checkpointing
>    Affects Versions: 1.2.0, 1.3.0
>            Reporter: Till Rohrmann
>
> The {{RocksDBStateBackend}} extracts the RocksDB jni library from the RocksDB dependency
in a temp directory (see {{RocksDBStateBackend#ensureRocksDBIsLoaded}}). This file is, however,
never removed. 
> In general, I think we should add a cleanup mechanism which cleans all {{Task}} specific
files after the {{Task}} has completed. The same applies to the {{TaskManager}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message