[
https://issues.apache.org/jira/browse/OOZIE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151515#comment-13151515
]
Mona Chitnis commented on OOZIE-565:
------------------------------------
After some testing with a .23 secure cluster, some findings..
The job is getting submitted as the superuser who "owns" or started the Oozie
service (say "oozie") rather than any authenticated user who is actually
submitting the job. For example say, "joe". Looks like a doAs error.
Diving into Oozie logs and also the "action.xml" conf file in the job's HDFS
working directory (created by Oozie),
The following properties are seen. User is "joe" as expected
<property>
<!--Loaded from Unknown-->
<name>hadoop.job.ugi</name>
<value>joe,users</value>
</property>
<property>
<!--Loaded from mapred-default.xml-->
<name>mapreduce.job.user.name</name>
<value>joe</value>
</property>
Now diving into Hadoop job container logs
2011-11-16 18:30:33,926 INFO [ContainerLauncher #0]
org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: The
job-conf file on the remote FS is
/user/oozie/.staging/job_1321387764123_0002/job.xml
Note that the home dir used is /user/oozie which should have been /user/joe
> Make Oozie compile against Hadoop 0.23
> --------------------------------------
>
> Key: OOZIE-565
> URL: https://issues.apache.org/jira/browse/OOZIE-565
> Project: Oozie
> Issue Type: Improvement
> Reporter: Roman Shaposhnik
> Assignee: Alejandro Abdelnur
>
--
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
