[
https://issues.apache.org/jira/browse/PIG-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286367#comment-14286367
]
Rohini Palaniswamy commented on PIG-4387:
-----------------------------------------
this.tezConf = new TezConfiguration(conf); - This tezConf in TezJobCompiler is
the one used for the DAG AM. But problem is even though tez-site.xml is added
last, it does not override because the setting does not come from yarn-site.xml
in conf but through config.set() from the properties in
ConfigurationUtil.toConfiguration(Properties properties, boolean loadDefaults).
If PigContext properties did not have the yarn-site.xml settings loaded into
it, it would have worked fine. So had to load tez-site.xml also into PigContext
properties.
bq. Sounds "yarn.timeline-service.enabled" is a yarn-site.xml entry, isn't it?
Yes. As we only wanted the timeline service enabled for tez jobs, trying to
enable it only in tez-site.xml.
> Honor yarn settings in tez-site.xml and optimize dag status fetch
> -----------------------------------------------------------------
>
> Key: PIG-4387
> URL: https://issues.apache.org/jira/browse/PIG-4387
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.14.0
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
> Fix For: 0.15.0
>
> Attachments: PIG-4387-1.patch
>
>
> When setting yarn.timeline-service.enabled=true in tez-site.xml, the value
> was still taken as false. This was because
> yarn.timeline-service.enabled=false in yarn-site.xml went into PigContext
> properties in Utils.recomputeProperties(jc, properties); and that took more
> precedence.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
