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-5903) taskmanager.numberOfTaskSlots and yarn.containers.vcores did not work well in YARN mode
Date Fri, 03 Mar 2017 10:42:45 GMT

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

ASF GitHub Bot commented on FLINK-5903:

Github user tillrohrmann commented on a diff in the pull request:

    --- Diff: flink-yarn/src/main/java/org/apache/flink/yarn/cli/FlinkYarnSessionCli.java
    @@ -537,7 +543,6 @@ public YarnClusterClient createCluster(
     		Preconditions.checkNotNull(userJarFiles, "User jar files should not be null.");
     		AbstractYarnClusterDescriptor yarnClusterDescriptor = createDescriptor(applicationName,
    -		yarnClusterDescriptor.setFlinkConfiguration(config);
    --- End diff --
    You cannot simply ignore the `configuration` which has been given to `createCluster`.
What if it contains configuration values which were added programmatically?

> taskmanager.numberOfTaskSlots and yarn.containers.vcores did not work well in YARN mode
> ---------------------------------------------------------------------------------------
>                 Key: FLINK-5903
>                 URL: https://issues.apache.org/jira/browse/FLINK-5903
>             Project: Flink
>          Issue Type: Bug
>          Components: YARN
>            Reporter: Tao Wang
>            Assignee: Tao Wang
>         Attachments: set taskmanager.numberOfTaskSlots to 6.JPG, set yarn.container.vcores
to 5_JM.JPG, set yarn.container.vcores to 5_RM.JPG
> Now Flink did not respect taskmanager.numberOfTaskSlots and yarn.containers.vcores in
flink-conf.yaml, but only -s parameter in CLI.
> Details is that taskmanager.numberOfTaskSlots is not working in anyway andyarn.containers.vcores
is only used in requesting container(TM) resources but not aware to TM, which means TM will
always think it has default(1) Slots if -s is not configured.

This message was sent by Atlassian JIRA

View raw message