Re: RocksDB checkpointing dir per TM

2018-11-07 Thread Till Rohrmann
This is a very good point Elias. We actually forgot to add these options to the configuration documentation after a refactoring. I will fix it. Cheers, Till On Fri, Oct 26, 2018 at 8:27 PM Elias Levy wrote: > There is also state.backend.rocksdb.localdir. Oddly, I can find the > documentation

Re: RocksDB checkpointing dir per TM

2018-10-26 Thread Elias Levy
There is also state.backend.rocksdb.localdir. Oddly, I can find the documentation for it in the 1.5 docs , but not in the 1.6 docs

Re: RocksDB checkpointing dir per TM

2018-10-26 Thread Taher Koitawala
Thanks! On Fri 26 Oct, 2018, 3:31 PM Andrey Zagrebin, wrote: > Hi Taher, > > TMs keep state locally while running, in this case RocksDB files already > belong to TM. > You can point it to the same NVME disk location on each node, relevant > Flink options here are: > - io.tmp.dirs > -

Re: RocksDB checkpointing dir per TM

2018-10-26 Thread Andrey Zagrebin
Hi Taher, TMs keep state locally while running, in this case RocksDB files already belong to TM. You can point it to the same NVME disk location on each node, relevant Flink options here are: - io.tmp.dirs - taskmanager.state.local.root-dirs This data is transient and has temporary nature. It

RocksDB checkpointing dir per TM

2018-10-26 Thread Taher Koitawala
Hi All, Our current cluster configuration uses one HDD which is mainly for root and an other NVME disk per node, [1]we want make sure all TMs write their own RocksDB files to the NVME disk only, how do we do that? [2] Is it also possible to specify multiple directories per TMs so that