[
https://issues.apache.org/jira/browse/TEZ-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259509#comment-17259509
]
Rajesh Balamohan commented on TEZ-4254:
---------------------------------------
[~mustafaiman] : There is some basic confusion on
"mapreduce.shuffle.ssl.enabled". This parameter is needed only in NM for its
shuffle handler and not needed in fetcher side of Tez. SSL in tez is controlled
by "tez.runtime.shuffle.ssl.enable" which can be passed as a flag at runtime.
Fixing it here may be concealing the potential root cause is my concern.
> Don't unset the tez config if both mr and tez config have same value.
> ---------------------------------------------------------------------
>
> Key: TEZ-4254
> URL: https://issues.apache.org/jira/browse/TEZ-4254
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.9.1
> Reporter: Rajkumar Singh
> Priority: Major
> Attachments: TEZ-4254.patch
>
>
> while translated mr config to the tez config we unset config here.
> https://github.com/apache/tez/blob/master/tez-mapreduce/src/main/java/org/apache/tez/mapreduce/hadoop/MRHelpers.java#L187
> There is no need to unset the config if both mr and tez have same value.
> we observed if equivalent of tez config for mapreduce.shuffle.ssl.enabled
> (tez.runtime.shuffle.ssl.enable) set to true, we unset the config, this
> propagate config
> tez.runtime.shuffle.ssl.enable={mapreduce.shuffle.ssl.enabled} at runtime and
> variable substitution does not work correctly in the absence of mrconfig
> runtime.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
