[
https://issues.apache.org/jira/browse/FLINK-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756815#comment-16756815
]
vinoyang commented on FLINK-11471:
----------------------------------
Currently, the transformation of {{JobStatus.RUNNING}} does not depend on the
state of any Task. Its state machine is completely independent on the JM side
(even without the need for the Task to be scheduled or executed). I think we
can make it more accurate according to the status report of the Task. For
example, we only change the JobStatus to RUNNING after receiving any Task
report "RUNNING".
> Job is reported RUNNING prematurely for queued scheduling
> ---------------------------------------------------------
>
> Key: FLINK-11471
> URL: https://issues.apache.org/jira/browse/FLINK-11471
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination, Scheduler
> Affects Versions: 1.7.1
> Reporter: Nico Kruber
> Assignee: vinoyang
> Priority: Major
>
> With queued scheduling enabled (seems to be the default now), the job's
> status is changed to RUNNING before all tasks are actually running.
> Although {{JobStatus#RUNNING}} states
> {quote}Some tasks are scheduled or running, some may be pending, some may be
> finished.{quote}
> you may argue whether this is the right thing to report, e.g. in the REST
> interface, when a user wants to react on the actual state change from
> SCHEDULED to RUNNING. It seems, some intermediate state is missing here which
> would clarify things.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
