[
https://issues.apache.org/jira/browse/TEZ-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308641#comment-14308641
]
Jonathan Eagles commented on TEZ-1160:
--------------------------------------
[~rramya], I think this issue has been solved by TEZ-1534. I am able to specify
yarn.timeline-service.enabled=true in my tez-site.xml and it is propagated
correctly even with yarn.timeline-service.enabled=false in cluster
yarn-site.xml file. Can you verify this is solved and this issue can be closed?
> Allow users to set non-tez configs on client side
> -------------------------------------------------
>
> Key: TEZ-1160
> URL: https://issues.apache.org/jira/browse/TEZ-1160
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Ramya Sunil
>
> We ran into an issue while testing ATS with tez. We wanted to validate if tez
> AM can write to ATS but we could not do this without updating configs on the
> entire cluster.
> Here is the exact scenario:
> 1. 10node cluster running with ats=disabled in yarn-site.xml
> 2. Set ATS=enabled on one host in the cluster and start ATS daemon before
> test execution
> 3. Submit a tez job with ats=enabled on cli/tez-site.xml to verify that tezAM
> writes to ATS.
> 4. Shutdown ATS.
> Step #3 will fail because tezAM reads configs deployed on the cluster i.e
> RM/NMs and in the configs deployed on the cluster ats=disabled, meaning tezAM
> does not write to ATS though the client side/tez-site.xml has set ats=enabled.
> As a workaround, we need to update the entire cluster with ats=enabled and
> restart services so that tezAM can write to ATS. It will be nice to have a
> feature in tez where users can set a non-tez config in tez-site.xml and that
> config is honored cluster wide for tez AM/tasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
