You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2016/02/08 18:46:39 UTC

[jira] [Commented] (FLINK-3372) Setting custom YARN application name is ignored

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

Fabian Hueske commented on FLINK-3372:
--------------------------------------

I think this is a duplicate of FLINK-3293 which was fixed for 1.0.0.
Unfortunately, the fix was not ported to the 0.10 branch. But since we just canceled the RC1 vote, we might add this fix to the next RC as well.

> Setting custom YARN application name is ignored
> -----------------------------------------------
>
>                 Key: FLINK-3372
>                 URL: https://issues.apache.org/jira/browse/FLINK-3372
>             Project: Flink
>          Issue Type: Bug
>          Components: YARN Client
>    Affects Versions: 0.10.1
>            Reporter: Nick Dimiduk
>
> The {{-ynm}} optional argument is ignored. From my debugging FlinkYarnClientBase does the right thing to parse and set the value. CliFrontend ignores this parsed value, always calling
> {noformat}
>             flinkYarnClient.setName("Flink Application: " + programName);
> {noformat}
> down in {{getClient(CommandLineOptions, String, int)}}. Thus every job submission to YARN is identifiable only by its classname.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)