Hi All!

I am experimenting with the ForSt state backend on 2.0.0 and I noticed the
following thing.

If I have a job with a larger state, let's say 500GB and now I want to
start the job with a lower parallelism on a single TaskManager, the job
will simply not start as the ForStIncrementalRestoreOperation tries to
download all states locally (there is not enough disk space)

I have these configs:

"state.backend.type": "forst"
"state.backend.forst.cache.size-based-limit": "10GB"

I assumed it will only download at most 10GB and just start reading from
remote and the job should start up "immediately".

What am I missing?

Gyula

Reply via email to