You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Liu (Jira)" <ji...@apache.org> on 2022/03/04 09:43:00 UTC

[jira] [Commented] (FLINK-26469) Adaptive job shows error in WebUI when not enough resource are available

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

Liu commented on FLINK-26469:
-----------------------------

I have met the problem before. When no resource is available, the jobGraph will not be built. So you can not check the job in the web. In this case, the meaningful exception message will be helpful. I wonder that whether a job DAG without any parallelism is ok?

> Adaptive job shows error in WebUI when not enough resource are available
> ------------------------------------------------------------------------
>
>                 Key: FLINK-26469
>                 URL: https://issues.apache.org/jira/browse/FLINK-26469
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>    Affects Versions: 1.15.0
>            Reporter: Niklas Semmler
>            Priority: Major
>
> When there is no resource and job is in CREATED state, the job page shows the error: "Job failed during initialization of JobManager". 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)