You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Mohammad Kamrul Islam (Created) (JIRA)" <ji...@apache.org> on 2011/11/22 21:02:39 UTC

[jira] [Created] (OOZIE-612) oozie examples' job properties doesn't contain principal name

oozie examples' job properties doesn't contain principal name
-------------------------------------------------------------

                 Key: OOZIE-612
                 URL: https://issues.apache.org/jira/browse/OOZIE-612
             Project: Oozie
          Issue Type: Bug
            Reporter: Mohammad Kamrul Islam
            Priority: Minor


Current properties are fine for hadoop 0.20 non-secured.
Currently more people are using Hadoop 0.20S which needs the two principal configurations.
The examples' job properties should include those principal with default values. However those props should be commented with text something like "please un-comment those for secured hadoop.

--
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

        

[jira] [Commented] (OOZIE-612) oozie examples' job properties doesn't contain principal name

Posted by "Harsh J (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413990#comment-13413990 ] 

Harsh J commented on OOZIE-612:
-------------------------------

I concur this problem still exists. It especially rears its head during re-run I think. One of the users reported the issue here: https://issues.cloudera.org/browse/DISTRO-334
                
> oozie examples' job properties doesn't contain principal name
> -------------------------------------------------------------
>
>                 Key: OOZIE-612
>                 URL: https://issues.apache.org/jira/browse/OOZIE-612
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Mohammad Kamrul Islam
>            Priority: Minor
>
> Current properties are fine for hadoop 0.20 non-secured.
> Currently more people are using Hadoop 0.20S which needs the two principal configurations.
> The examples' job properties should include those principal with default values. However those props should be commented with text something like "please un-comment those for secured hadoop.

--
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

        

[jira] [Commented] (OOZIE-612) oozie examples' job properties doesn't contain principal name

Posted by "Mohammad Kamrul Islam (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155548#comment-13155548 ] 

Mohammad Kamrul Islam commented on OOZIE-612:
---------------------------------------------

But I saw a user complain that he has to provide it in the job.properties.

Are you referring to this code?
defaultConf.set(WorkflowAppService.HADOOP_JT_KERBEROS_NAME, "mapred/_HOST@" + localRealm); defaultConf.set(WorkflowAppService.HADOOP_NN_KERBEROS_NAME, "hdfs/_HOST@" + localRealm);

These are part of one createFileSystem() and the other one doesn't have it . Do we need the same for createJobClient(). It is not there.
                
> oozie examples' job properties doesn't contain principal name
> -------------------------------------------------------------
>
>                 Key: OOZIE-612
>                 URL: https://issues.apache.org/jira/browse/OOZIE-612
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Mohammad Kamrul Islam
>            Priority: Minor
>
> Current properties are fine for hadoop 0.20 non-secured.
> Currently more people are using Hadoop 0.20S which needs the two principal configurations.
> The examples' job properties should include those principal with default values. However those props should be commented with text something like "please un-comment those for secured hadoop.

--
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

        

[jira] [Commented] (OOZIE-612) oozie examples' job properties doesn't contain principal name

Posted by "Alejandro Abdelnur (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155401#comment-13155401 ] 

Alejandro Abdelnur commented on OOZIE-612:
------------------------------------------

What principal names are we referring to? the JT and NN? If so, the KerberosHadoopAccessorService injects the rules for them. I've run the examples against Kerberos setup without changes.
                
> oozie examples' job properties doesn't contain principal name
> -------------------------------------------------------------
>
>                 Key: OOZIE-612
>                 URL: https://issues.apache.org/jira/browse/OOZIE-612
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Mohammad Kamrul Islam
>            Priority: Minor
>
> Current properties are fine for hadoop 0.20 non-secured.
> Currently more people are using Hadoop 0.20S which needs the two principal configurations.
> The examples' job properties should include those principal with default values. However those props should be commented with text something like "please un-comment those for secured hadoop.

--
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