[
https://issues.apache.org/jira/browse/OOZIE-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413115#comment-13413115
]
Virag Kothari commented on OOZIE-878:
-------------------------------------
Kerberos Name rules are only present on the server side. Once HADOOP-8518, we
will have it on client side too. This is required on the client to resolve the
server name before getting the ticket. If server has an alias, it should be
resolved to actual host name so that the KDC doesn't complain. Mapping of
aliases to actual host name can be done in Oozie's client xml.
Related to job.properties question, I think Oozie in general can connect to
multiple hadoop clusters. So, user needs to specify the JT/NN they want to
connect to.
> Add oozie-client-site.xml configuration file
> --------------------------------------------
>
> Key: OOZIE-878
> URL: https://issues.apache.org/jira/browse/OOZIE-878
> Project: Oozie
> Issue Type: Improvement
> Components: client
> Affects Versions: 3.2.0
> Reporter: Alejandro Abdelnur
> Fix For: trunk
>
>
> the number of settings on the client side is growing and we cannot get away
> (cleanly) with the current mechanism (EVNs or modifying the oozie script).
> We should introduce a conf/oozie-client-site.xml file where we can do such
> settings.
> For example: OOZIE_URL, authenticator class, if the authentication cookie
> should be saved to file, etc.
> This will also help for defining the KerberosName rules for the client side
> whe HADOOP-8518 goes in.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
