You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@flink.apache.org by makeyang <ri...@hotmail.com> on 2018/05/25 11:27:35 UTC

does Flink call FullGC to reclaim direct memory mainly occupied by RocksDB

each time when cancel Job does Flink call FullGC to reclaim direct memory
mainly occupied by RocksDB?
if so, where does this?
if not, why?



--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/

Re: does Flink call FullGC to reclaim direct memory mainly occupied by RocksDB

Posted by sihua zhou <su...@163.com>.

Hi,

I think each time when canceling the job, flink will close the RocksDB to release the resource held by it. You can find this in RocksDBKeyedStateBackend.

Best, Sihua



On 05/25/2018 19:27, makeyang wrote:
each time when cancel Job does Flink call FullGC to reclaim direct memory
mainly occupied by RocksDB?
if so, where does this?
if not, why?



--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/