Job execution graph state - INITIALIZING

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Job execution graph state - INITIALIZING

Nikola Hrusov
Hello,

I have looked into this issue: https://issues.apache.org/jira/browse/FLINK-16866 which supposedly adds "INITIALIZING" state.

I tried to find the documentation here:

But I could not find any more information on that particular job state. On the first link in the docs it says "A Flink job is first in the created state" 

Can I get more information on that state? Is "INITIALIZING" first or is it "CREATED"? How/when do we get into "INITIALIZING" and when do we get out of it? Would that happen for both stream and batch jobs?

I hope you can help me with some answers on my questions.

Regards
,
Nikola

Reply | Threaded
Open this post in threaded view
|

Re: Job execution graph state - INITIALIZING

Chesnay Schepler
INITIALIZING is the very first state a job is in.
It is the state of a job that has been accepted by the JobManager, but the processing of said job has not started yet.
In other words, INITIALIZING = submitted job, CREATED = data-structures and components required for scheduling have been created.
Internally, this means means that no JobMaster nor ExecutionGraph has been created yet.

This applies to all jobs.

On 1/24/2021 5:58 PM, Nikola Hrusov wrote:
Hello,

I have looked into this issue: https://issues.apache.org/jira/browse/FLINK-16866 which supposedly adds "INITIALIZING" state.

I tried to find the documentation here:

But I could not find any more information on that particular job state. On the first link in the docs it says "A Flink job is first in the created state" 

Can I get more information on that state? Is "INITIALIZING" first or is it "CREATED"? How/when do we get into "INITIALIZING" and when do we get out of it? Would that happen for both stream and batch jobs?

I hope you can help me with some answers on my questions.

Regards
,
Nikola