You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Miomir Boljanovic (JIRA)" <ji...@apache.org> on 2015/12/08 13:09:10 UTC
[jira] [Assigned] (MAPREDUCE-6565) Configuration to use host name
in delegation token service is not read from job.xml during MapReduce job
execution.
[ https://issues.apache.org/jira/browse/MAPREDUCE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Miomir Boljanovic reassigned MAPREDUCE-6565:
--------------------------------------------
Assignee: Miomir Boljanovic
> Configuration to use host name in delegation token service is not read from job.xml during MapReduce job execution.
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6565
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6565
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Chris Nauroth
> Assignee: Miomir Boljanovic
>
> By default, the service field of a delegation token is populated based on server IP address. Setting {{hadoop.security.token.service.use_ip}} to {{false}} changes this behavior to use host name instead of IP address. However, this configuration property is not read from job.xml. Instead, it's read from a separate {{Configuration}} instance created during static initialization of {{SecurityUtil}}. This does not work correctly with MapReduce jobs if the framework is distributed by setting {{mapreduce.application.framework.path}} and the {{mapreduce.application.classpath}} is isolated to avoid reading core-site.xml from the cluster nodes. MapReduce tasks will fail to authenticate to HDFS, because they'll try to find a delegation token based on the NameNode IP address, even though at job submission time the tokens were generated using the host name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)