[
https://issues.apache.org/jira/browse/HADOOP-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated HADOOP-12954:
-----------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.9.0
Status: Resolved (was: Patch Available)
Thanks for the review Steve. Committed to trunk and branch-2!
> Add a way to change hadoop.security.token.service.use_ip
> --------------------------------------------------------
>
> Key: HADOOP-12954
> URL: https://issues.apache.org/jira/browse/HADOOP-12954
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.6.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: 2.9.0
>
> Attachments: HADOOP-12954.001.patch, HADOOP-12954.002.patch,
> HADOOP-12954.003.patch
>
>
> Currently, {{hadoop.security.token.service.use_ip}} is set on JVM startup via:
> {code:java}
> static {
> Configuration conf = new Configuration();
> boolean useIp = conf.getBoolean(
> CommonConfigurationKeys.HADOOP_SECURITY_TOKEN_SERVICE_USE_IP,
> CommonConfigurationKeys.HADOOP_SECURITY_TOKEN_SERVICE_USE_IP_DEFAULT);
> setTokenServiceUseIp(useIp);
> }
> {code}
> This is a problem for clients, such as Oozie, who don't add *-site.xml files
> to their classpath. Oozie normally creates a {{JobClient}} and passes a
> {{Configuration}} to it with the proper configs we need. However, because
> {{hadoop.security.token.service.use_ip}} is specified in a static block like
> this, and there's no API to change it, Oozie has no way to set it to the
> non-default value.
> I propose we add a {{setConfiguration}} method which takes a
> {{Configuration}} and rereads {{hadoop.security.token.service.use_ip}}.
> There's a few other properties that are also loaded statically on startup
> that can be reloaded here as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
