[
https://issues.apache.org/jira/browse/FLINK-24824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler updated FLINK-24824:
-------------------------------------
Parent: FLINK-21510
Issue Type: Sub-task (was: Bug)
> AdaptiveScheduler#getJobStatus never returns CREATED
> ----------------------------------------------------
>
> Key: FLINK-24824
> URL: https://issues.apache.org/jira/browse/FLINK-24824
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Fix For: 1.15.0
>
>
> None of the AdaptiveScheduler states return {{JobStatus#CREATED}} when
> {{requestJobStatus()}} is called. This violates the job state machine, and
> makes it a bit difficult to setup job state timestamps in the
> {{AdaptiveScheduler}} (FLINK-24775).
> We are in the {{INITIALIZING}} state from {{Created}} ->
> {{WaitingForResources}} -> {{CreatingExecutionGraph}}, and then switch
> straight to RUNNING in {{Executing}}.
> It is tricky to retain the same semantics for the {{Default}} and
> {{AdaptiveScheduler}}, but I think it would be fine to return {{CREATED}}
> once we reached {{WaitingForResources}} because from the users-perspective it
> behaves similarly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
