You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/02/19 14:52:00 UTC

[jira] [Updated] (FLINK-16005) Propagate yarn.application.classpath from client to TaskManager Classpath

     [ https://issues.apache.org/jira/browse/FLINK-16005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann updated FLINK-16005:
----------------------------------
    Description: When Flink users want to override the hadoop yarn container classpath, they should just specify the yarn.application.classpath in yarn-site.xml from cli side. But currently, the classpath setting can only be used in flink application master, the classpath of TM is still determined by the setting in yarn host.  (was: When Flink users what to override the hadoop yarn container classpath, they should just specify the yarn.application.classpath in yarn-site.xml from cli side. But currently, the classpath setting can only be used in flink application master, the classpath of TM is still determined by the setting in yarn host.)

> Propagate yarn.application.classpath from client to TaskManager Classpath
> -------------------------------------------------------------------------
>
>                 Key: FLINK-16005
>                 URL: https://issues.apache.org/jira/browse/FLINK-16005
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / YARN
>            Reporter: Zhenqiu Huang
>            Priority: Critical
>
> When Flink users want to override the hadoop yarn container classpath, they should just specify the yarn.application.classpath in yarn-site.xml from cli side. But currently, the classpath setting can only be used in flink application master, the classpath of TM is still determined by the setting in yarn host.



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