[FLINK-10882] Misleading job/task state for scheduled jobs

• Type: Bug
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Affects Version/s: 1.7.0
• Component/s: Runtime / Web Frontend
• Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned
• Assignee: Unassigned
• Reporter: Chesnay Schepler
• Created: 14/Nov/18 13:41
• Updated: 26/Dec/21 10:39

Description

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

1. States the task is in a CREATED state, when it is actually SCHEDULED
2. States the task is in a CREATED state, but the count for all state boxes is zero.
   (see task_view attachment)

Issue Links

• is duplicated by: FLINK-11471 Job is reported RUNNING prematurely for queued scheduling