[ 
https://issues.apache.org/jira/browse/FLINK-9055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425422#comment-16425422
 ] 

Fabian Hueske commented on FLINK-9055:
--------------------------------------

Hi [~sihuazhou], thanks for taking care of this issue.

No, I don't think we should fail a job immediately when there are not enough 
resources. With the dynamic resource allocation feature of Flink 1.5, TMs can 
be spawned and register to the JM after a job was submitted. This does not work 
for stand-alone clusters which do not leverage a resource manager (YARN, Mesos, 
Kubernetes).

However, a job waiting for resources should not be displayed as running because 
it is not running yet (or will never be able to run in case of a stand-alone 
setup).

I don't know what would be the best solution for this issue. However, we should 
avoid changing the lifecycle states of a job.

> 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)

Reply via email to