hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4490) Map and Reduce tasks should run as the user who submitted the job
Date Thu, 05 Feb 2009 16:31:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670819#action_12670819

Hemanth Yamijala commented on HADOOP-4490:

Attached a hopefully last version of the patch. This one is extensively tested and has fixed
a couple of bugs related to incorrect assumptions about multiple mapred local directories.
Thanks to Sreekanth and Amar for help in testing this. We're run randomwriter, sort with and
without JVM reuse, and also streaming and using distributed cache.

The test-patch results are showing a -1 on release audit which I've written to core-dev about.
I am not sure why a -1 is coming, will continue to debug that. There's also a -1 on tests.
It is difficult to write unit tests for this patch since it requires support for multiple

There are a lot of log statements in the patch which should be removed before commit. I am
attaching this with the hope that someone can take a look at the changes. Arun ?

> Map and Reduce tasks should run as the user who submitted the job
> -----------------------------------------------------------------
>                 Key: HADOOP-4490
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4490
>             Project: Hadoop Core
>          Issue Type: Sub-task
>          Components: mapred, security
>            Reporter: Arun C Murthy
>            Assignee: Hemanth Yamijala
>         Attachments: hadoop-4490-design.pdf, HADOOP-4490.patch, HADOOP-4490.patch, HADOOP-4490.patch,
HADOOP-4490.patch, HADOOP-4490.patch
> Currently the TaskTracker spawns the map/reduce tasks, resulting in them running as the
user who started the TaskTracker.
> For security and accounting purposes the tasks should be run as the job-owner.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message