You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "lining (JIRA)" <ji...@apache.org> on 2019/01/17 03:07:00 UTC
[jira] [Issue Comment Deleted] (FLINK-10882) Misleading job/task
state for scheduled jobs
[ https://issues.apache.org/jira/browse/FLINK-10882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lining updated FLINK-10882:
---------------------------
Comment: was deleted
(was: See code, now org.apache.flink.runtime.jobgraph.JobStatus define running which means
Some tasks are scheduled or running, some may be pending, some may be finished. Should we add new status?)
> Misleading job/task state for scheduled jobs
> --------------------------------------------
>
> Key: FLINK-10882
> URL: https://issues.apache.org/jira/browse/FLINK-10882
> Project: Flink
> Issue Type: Bug
> Components: Webfrontend
> Affects Versions: 1.7.0
> Reporter: Chesnay Schepler
> Priority: Major
> Attachments: list_view.png, task_view.png
>
>
> When submitting a job when not enough resources are available currently cuases the job stay in a {{CREATE/SCHEDULED}} state.
> There are 2 issues with how this is presented in the UI.
> The {{Running Jobs}} page incorrectly states that the job is running.
> (see list_view attachment)
> EDIT: Actually, from a runtime perspective the job is in fact in a RUNNING state.
> The state display for individual tasks either
> # States the task is in a CREATED state, when it is actually SCHEDULED
> # States the task is in a CREATED state, but the count for all state boxes is zero.
> (see task_view attachment)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)