[
https://issues.apache.org/jira/browse/FLINK-9055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427032#comment-16427032
]
Sihua Zhou commented on FLINK-9055:
-----------------------------------
Hi [~fhueske], thanks for your reply, I was thinking that changing the
lifecycle states maybe the most natural way to solve this problem, but that way
means we need a really big change for the current code, so as you pointed out
we should avoid changing the lifecycle states, I agree it. And before
implementing the code, I'd like to have a bit discussion on this issue, cause I
don't know what would be the best solution for this issue either... My current
work-around is when we {{requestJobStatus}}, we won't always just return the
{{executionGraph.getState()}}, when {{executionGraph.getState() == RUNNING}} we
need do a double-check to check the {{Executions}} that belong to the
{{ExecutionGraph}}. What do you think of this work-around?
> WebUI shows job as Running although not enough resources are available
> ----------------------------------------------------------------------
>
> Key: FLINK-9055
> URL: https://issues.apache.org/jira/browse/FLINK-9055
> Project: Flink
> Issue Type: Bug
> Components: JobManager, Webfrontend
> Affects Versions: 1.5.0
> Environment: * FLIP-6 enabled
> * Local Flink instance with fixed number of TMs
> * Job parallelism exceeds available slots
> Reporter: Fabian Hueske
> Assignee: Sihua Zhou
> Priority: Major
>
> The WebUI shows a (batch) job as "Running" although not enough resources have
> been allocated to actually run the job with the requested parallelism.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
