[
https://issues.apache.org/jira/browse/FLINK-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986195#comment-16986195
]
Andrey Zagrebin commented on FLINK-14378:
-----------------------------------------
[~yunta]
>From what I see this issue is about the case where something fails and the
>directory stays
I think FLINK-15011 is about the case where the cluster is gracefully shutdown
and the contents of the directory is cleaned but not the directory itself.
Are you sure the cause is the same?
I will assign you anyways to the issue
[~NicoK] could you also check this issue?
> Cleanup rocksDB lib folder if fail to load library
> --------------------------------------------------
>
> Key: FLINK-14378
> URL: https://issues.apache.org/jira/browse/FLINK-14378
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Reporter: Yun Tang
> Priority: Major
>
> This improvement is inspired due to some of our machines need some time to
> load the rocksDB library. When some other unrecoverable exceptions continue
> to happen and the process to load library would be interrupted which cause
> the {{rocksdb-lib}} folder created but not cleaned up. As the job continues
> to failover, the {{rocksdb-lib}} folder would be created more and more. We
> even come across that machine was running out of inodes!
> Details could refer to current
> [implementation|https://github.com/apache/flink/blob/80b27a150026b7b5cb707bd9fa3e17f565bb8112/flink-state-backends/flink-statebackend-rocksdb/src/main/java/org/apache/flink/contrib/streaming/state/RocksDBStateBackend.java#L860]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
