With Flink 1.5.x and 1.6.x you can put `mode: legacy` into your flink-conf.yaml and it will start the old mode. Then you have the old behaviour.
What do you mean with total slots? The current number of total slots? With resource elasticity this number can of course change because if you don't have enough slots, then Flink will try to start a new TaskExecutor. Cheers, Till On Mon, Sep 24, 2018 at 7:11 PM suraj7 <su...@amagi.com> wrote: > Thanks for the clarification, Dawid and Till. > > @Till We have a few streaming jobs that need to be running all the time and > we plan on using the modify tool to update parallelism of jobs as we scale > the cluster in and out and knowing total slots value is crucial to this > workflow. > > As Dawid pointed out, is there a switch to restore the old behavior? > If not, is there a way to find/predict total slots value from YARN metrics? > Are you aware of any such workflow? > > Thanks, > Suraj > > > > -- > Sent from: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ >
