You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:25:09 UTC
[jira] [Commented] (OOZIE-70) GH-24: leverage Hadoop rules for
JT/NN Kerberos principal resolution
[ https://issues.apache.org/jira/browse/OOZIE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099766#comment-13099766 ]
Hadoop QA commented on OOZIE-70:
--------------------------------
tucu00 remarked:
Closed by 3045020b9ec74fda9afac0d83484a642e1549a56 leverage Hadoop rules for JT/NN Kerberos principal resolution
Currently Oozie requires the JT and NN kerberos principals to be in the WF job
properties when submitting a job.
Hadoop has built in rules to create these principals (i.e. mapred/_HOST@${local.realm}).
Oozie should leverage those rules if the WF job properties do not include JT/NN kerberos
principals thus not requiring them as mandatory WF job properties on WF submission.
> GH-24: leverage Hadoop rules for JT/NN Kerberos principal resolution
> --------------------------------------------------------------------
>
> Key: OOZIE-70
> URL: https://issues.apache.org/jira/browse/OOZIE-70
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> Currently Oozie requires the JT and NN kerberos principals to be in the WF job properties when submitting a job.
> Hadoop has built in rules to create these principals (i.e. mapred/_HOST@${local.realm}).
> Oozie should leverage those rules if the WF job properties do not include JT/NN kerberos principals thus not requiring them as mandatory WF job properties on WF submission.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira