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.
Attachments
Attachments
Issue Links
- duplicates
-
TEZ-1538 Tez Local Mode fails if "fs.defaultFS" is not set to be "file:///' in core-site.xml
-
- Resolved
-
-
TEZ-1160 Allow users to set non-tez configs on client side
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
- is related to
-
-
- Resolved
-