The backpressure is caused when downstream and upstream are running concurrently, and the downstream is slower than the upstream. In stream job, the schedule mode will schedule both sides concurrently, so the backpressure may exist. As for batch job, the default schedule mode is LAZY_FROM_SOURCE I remember, that means the downstream will be scheduled after upstream finishes, so the slower downstream will not block upstream running, then the backpressure may not exist in this case.
Best, Zhijiang ------------------------------------------------------------------ 发件人:Darshan Singh <darshan.m...@gmail.com> 发送时间:2018年8月29日(星期三) 16:20 收件人:user <user@flink.apache.org> 主 题:Backpressure? for Batches I faced the issue with back pressure in streams. I was wondering if we could face the same with the batches as well. In theory it should be possible. But in Web UI for backpressure tab for batches I was seeing that it was just showing the tasks status and no status like "OK" etc. So I was wondering if backpressure is a thing for batches. If yes, how do we reduce this especially if I am reading from hdfs. Thanks