[TEZ-1534] Make client side configs available to AM and tasks

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.5.1
• Target Version/s: 0.5.1
• Assignee: Siddharth Seth
• Reporter: Siddharth Seth
• Created: 03/Sep/14 05:44
• Updated: 13/Mar/15 01:10
• Resolved: 11/Sep/14 07:21

Description

Configs from the client (specifically the ones provided to TezClient, along with YARN additions) should be shipped over to the cluster (AM and tasks), instead of AM/tasks depending on configs present on cluster nodes.

These configs will primarily be used for Tez components like RPC servers, clients etc - and not by the Processor / Input / Output - which should be sending over fully configured payloads in any case.

Tez should continue to run without core-site, hdfs-site, yarn-site etc in the classpath on cluster nodes.

Issue Links

• duplicates: TEZ-1538 Tez Local Mode fails if "fs.defaultFS" is not set to be "file:///' in core-site.xml
• duplicates: TEZ-1160 Allow users to set non-tez configs on client side
• is duplicated by: TEZ-1160 Allow users to set non-tez configs on client side
• is related to: TEZ-1538 Tez Local Mode fails if "fs.defaultFS" is not set to be "file:///' in core-site.xml