For the per-job cluster: Yes, the JobManager is started exclusively for the job.
For the Yarn session: No, the JobManager stays alive during the entire
session and may execute one or more jobs (one after another or even at
the same time).
On Mon, Mar 7, 2016 at 6:37 PM, Stefano Baghino
wrote:
>
One last question: running multiple jobs mean that each one has its own
JobManager, right?
On Mon, Mar 7, 2016 at 3:14 PM, Stefano Baghino <
stefano.bagh...@radicalbit.io> wrote:
> Good, thank you for the explanation!
>
> On Mon, Mar 7, 2016 at 2:38 PM, Maximilian Michels wrote:
>
>> Hi Stefano,
Good, thank you for the explanation!
On Mon, Mar 7, 2016 at 2:38 PM, Maximilian Michels wrote:
> Hi Stefano,
>
> Essentially the Yarn Session is not much different from a per-job Yarn
> cluster. In either case, a Flink cluster is brought up with resources
> provided by Yarn. In case of the Yarn
Hi Stefano,
Essentially the Yarn Session is not much different from a per-job Yarn
cluster. In either case, a Flink cluster is brought up with resources
provided by Yarn. In case of the Yarn session this cluster doesn't do
anything until a job is submitted. In case of the per-job Yarn
cluster, a j
