Thank you everyone for the clarification. It looks like the Rescale API
will require some more work before it can be fully taken advantage of. I'm
wondering whether in addition to the Rescale API we want to provide a means
to do a rescale without an explicit API call but as part of the job
submissi
Thanks for the attention to the rescale api. Dynamic resource adjust is
useful for streaming jobs since the throughput can change in different
time. The rescale api is a lightweight way to change the job's parallelism.
This is importance for some jobs, for example, the jobs are in activities
or rel
The AdaptiveScheduler is not limited to reactive mode. There are no
deployment limitations for the scheduler itself.
In a nutshell, all that reactive mode does is crank the target
parallelism to infinity, when usually it is the parallelism the user has
set in the job/configuration.
I think it
Hey Gyula,
Is the Adaptive Scheduler limited to the Reactive mode? I agree that if we
move forward with the Adaptive Scheduler solution it should support all
deployment scenarios.
Thanks,
-Max
On Sun, Oct 9, 2022 at 6:10 AM Gyula Fóra wrote:
> Hi!
>
> I think we have to make sure that the Resc
Hi!
I think we have to make sure that the Rescale API will work also without
the adaptive scheduler (for instance when we are running Flink with the
Kubernetes Native Integration or in other cases where the adaptive
scheduler is not supported).
What do you think?
Cheers
Gyula
On Fri, Oct 7, 2
