flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-6189) Do not use yarn client config to do sanity check
Date Fri, 19 Oct 2018 08:19:00 GMT

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

ASF GitHub Bot commented on FLINK-6189:

GJL commented on issue #3614: [FLINK-6189][YARN]Do not use yarn client config to do sanity
URL: https://github.com/apache/flink/pull/3614#issuecomment-431283709
   #6775 fixes the issue by querying the RM for the vcores. If you have objections with this
approach, feel free to open a new issue.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> 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
>            Priority: Major
> 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

View raw message