You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2021/01/27 03:47:00 UTC

[jira] [Commented] (FLINK-21153) yarn-per-job deployment target ignores yarn options

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

Yang Wang commented on FLINK-21153:
-----------------------------------

IIUC, this is the expected behavior. Because {{-t,--target}} will always active the {{GenericCLI}}. Actually, {{FlinkYarnSessionCli}} should be deprecated and removed in the future. But it seems it is widely used(from command line submission) and we could not do it right now.

> yarn-per-job deployment target ignores yarn options
> ---------------------------------------------------
>
>                 Key: FLINK-21153
>                 URL: https://issues.apache.org/jira/browse/FLINK-21153
>             Project: Flink
>          Issue Type: Bug
>          Components: Command Line Client, Deployment / YARN
>    Affects Versions: 1.13.0, 1.12.1
>            Reporter: Till Rohrmann
>            Priority: Major
>              Labels: usability
>             Fix For: 1.13.0, 1.12.2
>
>
> While looking into the problem reported in FLINK-6949, I stumbled across an odd behaviour of Flink. I tried to deploy a Flink cluster on Yarn and ship some files to the cluster. Only the first command successfully shipped the additional files to the cluster:
> 1) {{bin/flink run -p 1 --yarnship ../flink-test-job/cluster -m yarn-cluster ../flink-test-job/target/flink-test-job-1.0-SNAPSHOT.jar}}
> 2) {{bin/flink run -p 1 --yarnship ../flink-test-job/cluster -t yarn-per-job ../flink-test-job/target/flink-test-job-1.0-SNAPSHOT.jar}} 
> The problem seems to be that the second command does not activate the {{FlinkYarnSessionCli}} but uses the {{GenericCLI}}.
> [~kkl0u], [~aljoscha], [~tison] what is the intended behaviour in this case. I always thought that {{-m yarn-cluster}} and {{-t yarn-per-job}} would be equivalent.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)