Hi Ben,
I think at the moment, it is not possible because of current scheduling
design which Xintong has already mentioned.
The jobs are completely isolated and there is no synchronisation between
their deployment.
Alignment of tasks by e.g. key groups in general is difficult as it is up
to the sc
>
> Do you believe the code of the operators of the restarted Region can be
> changed between restarts?
I'm not an expert on the restart strategies, but AFAIK the answer is
probably not. Sorry I overlooked that you need to modify the job.
Thank you~
Xintong Song
On Tue, Feb 25, 2020 at 6:00
Hi Xintong
Thank you for your answer. This seems promising, I'll look into it.
Do you believe the code of the operators of the restarted Region can be
changed between restarts?
Best
Benoît
On Tue, Feb 25, 2020 at 2:30 AM Xintong Song wrote:
> Hi Ben,
>
> You can not share slots across jobs.
Hi Ben,
You can not share slots across jobs. Flink adopts a two-level slot
scheduling mechanism. Slots are firstly allocated to each job, then the
JobMaster decides which tasks should be executed in which slots, i.e. slot
sharing.
I think what you are looking for is Pipelined Region Restart Strat
Hello all!
I have a setup composed of several streaming pipelines. These have
different deployment lifecycles: I want to be able to modify and redeploy
the topology of one while the other is still up. I am thus putting them in
different jobs.
The problem is I have a Co-Location constraint between
