hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-871) Job/Task local files have incorrect group ownership set by LinuxTaskController binary
Date Thu, 20 Aug 2009 09:57:14 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod K V updated MAPREDUCE-871:
--------------------------------

    Attachment: MAPREDUCE-871-20090820.1.txt

Here's the scenario.
{quote}
                          TT process user/group information: mapred group1,group2,group3 (group1
is primary)
                          task-controller ownership: ---Sr-s--- 1 root  group2
                          job submitter: userA:groupA
{quote}

The bug is the ownership of files created for the task, for e.g.
bq. $jobid dr-xrws--- userA group1

Attaching patch to fix this issue which essentially sets the permissions of files created
for the task as
bq. $jobid dr-xrws--- userA group2

Also modified the testcase to reflect this.

> Job/Task local files have incorrect group ownership set by LinuxTaskController binary
> -------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-871
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-871
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: tasktracker
>            Reporter: Vinod K V
>            Assignee: Vinod K V
>         Attachments: MAPREDUCE-871-20090820.1.txt
>
>
> HADOOP-4491 fixed the secure permissions of local files on a TT. While testing HADOOP-4491
on a cluster, [~karams] found out a bug. All the files/dirs have should be owned by the group
corresponding to the group owner of the task-controller binary (via using getegid()) which
in turn is a special group to which *only* TT user belongs. HADOOP-4491 incorrectly set it
to primary group of the TT via getgid(), and not the special group.

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


Mime
View raw message