Hello,
I am running a streaming job on a small cluster, and after a few hours I
noticed that my TaskManager processes are being killed by the OOM killer. The
processes were using too much memory. After a bit of monitoring, I have the
following status:
* The maximum heap size (Xmx) is 4
This sounds like a RocksDB issue. Maybe Stefan (in CC) has an idea?
Timo
Am 17/01/17 um 14:52 schrieb Avihai Berkovitz:
Hello,
I am running a streaming job on a small cluster, and after a few hours
I noticed that my TaskManager processes are being killed by the OOM
killer. The processes we
Hi,
The answer to question one is clearly yes, and you can configure RocksDB
through the DBOptions.
Question two is obviously more tricky with the given information. But it is
surely possible that some resources are not properly released. All classes from
the RocksDB Java API have a safety net
