[
https://issues.apache.org/jira/browse/FLINK-10882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16776471#comment-16776471
]
vinoyang commented on FLINK-10882:
----------------------------------
Hi [~Zentol] I think this is not just an issue of web frontend. It is because
Job Status and Task Execution State are not connected in the {{RUNNING}} state.
I personally think that we should wait until a Task Execution State reports
{{RUNNING}} before setting the Job Status to {{RUNNING}}. What do you think?
> 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
> Assignee: vinoyang
> 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)
