hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John George (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3443) Oozie jobs are running as oozie user even though they create the jobclient as doAs.
Date Tue, 29 Nov 2011 18:25:41 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159422#comment-13159422

John George commented on MAPREDUCE-3443:

Tested the patch with oozie on a cluster. The patch seemed to work as long as in JobClient.submitJob(),
when we do a Job.getInstance(), we do it with the conf passed in by the user - Job.getInstance(conf).
After that the oozie web UI displayed 'success' and the job passed. 

Good job Mahadev.
> Oozie jobs are running as oozie user even though they create the jobclient as doAs.
> -----------------------------------------------------------------------------------
>                 Key: MAPREDUCE-3443
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3443
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Mahadev konar
>            Assignee: Mahadev konar
>            Priority: Blocker
>             Fix For: 0.23.1
>         Attachments: MAPREDUCE-3443.patch, MAPREDUCE-3443.patch, MAPREDUCE-3443.patch
> Oozie is having issues with job submission, since it does the following:
> {code}
> doAs(userwhosubmittedjob) {
>  jobclient = new JobClient(jobconf);
> }
> jobclient.submitjob()
> {code}
> In 0.20.2** this works because the JT proxy is created as soon as we call new JobClient().
But in 0.23 this is no longer true since the client has to talk to multiple servers (AM/RM/JHS).
To keep this behavior we will have to store the ugi in new JobClient() and make sure all the
calls are run with a doAs() inside the jobclient.

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


View raw message