[
https://issues.apache.org/jira/browse/FLINK-16005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035101#comment-17035101
]
Yang Wang commented on FLINK-16005:
-----------------------------------
I think this behavior is by design for Yarn. The jobmanager(i.e. application
master) use the cluster yarn-site.xml to initialize the {{YarnConfiguration}}.
If you do not want this happen, you should ship your own yarn configurations
from client.
> 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 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
