You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Nico Kruber (JIRA)" <ji...@apache.org> on 2019/01/30 16:14:00 UTC

[jira] [Created] (FLINK-11471) Job is reported RUNNING prematurely for queued scheduling

Nico Kruber created FLINK-11471:
-----------------------------------

             Summary: 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


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)