You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Johannes (JIRA)" <ji...@apache.org> on 2016/01/29 01:02:39 UTC
[jira] [Assigned] (FLINK-3293) Custom Application Name on YARN is
ignored in deploy jobmanager mode
[ https://issues.apache.org/jira/browse/FLINK-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johannes reassigned FLINK-3293:
-------------------------------
Assignee: Johannes
> Custom Application Name on YARN is ignored in deploy jobmanager mode
> --------------------------------------------------------------------
>
> Key: FLINK-3293
> URL: https://issues.apache.org/jira/browse/FLINK-3293
> Project: Flink
> Issue Type: Bug
> Components: YARN Client
> Affects Versions: 0.10.1
> Reporter: Johannes
> Assignee: Johannes
> Priority: Minor
>
> FLINK-2298 introduced a custom name for the job.
> This is ignored when the yarn application is started as part of the job submission, e.g.
> flink run -m yarn-cluster -ynm myname
> It is always set using the classname as program name
> flinkYarnClient.setName("Flink Application: " + programName);
> The client get's constructed using
> AbstractFlinkYarnClient flinkYarnClient = CliFrontendParser.getFlinkYarnSessionCli().createFlinkYarnClient(commandLine);
> So the name will be parsed correctly, it is just overwritten.
> This should be a fallback, when no name is provided
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)