[
https://issues.apache.org/jira/browse/FLINK-21153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322855#comment-17322855
]
Flink Jira Bot commented on FLINK-21153:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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.12.1, 1.13.0
> Reporter: Till Rohrmann
> Assignee: Dawid Wysakowicz
> Priority: Major
> Labels: stale-assigned, usability
> Fix For: 1.13.0, 1.12.3
>
>
> 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)
