flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tao Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-6189) Do not use yarn client config to do sanity check
Date Mon, 27 Mar 2017 07:47:41 GMT

     [ https://issues.apache.org/jira/browse/FLINK-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tao Wang updated FLINK-6189:
----------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: FLINK-5839

> Do not use yarn client config to do sanity check
> ------------------------------------------------
>
>                 Key: FLINK-6189
>                 URL: https://issues.apache.org/jira/browse/FLINK-6189
>             Project: Flink
>          Issue Type: Sub-task
>          Components: YARN
>            Reporter: Tao Wang
>            Assignee: Tao Wang
>
> Now in client, if #slots is greater than then number of "yarn.nodemanager.resource.cpu-vcores"
in yarn client config, the submission will be rejected.
> It makes no sense as the actual vcores of node manager is decided in cluster side, but
not in client side. If we don't set the config or don't set the right value of it(indeed this
config is not a mandatory), it should not affect flink submission.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message