[MAPREDUCE-842] Per-job local data on the TaskTracker node should have right access-control

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.21.0
• Component/s: security, task-controller, tasktracker
• Hadoop Flags: Reviewed

Release Note

Modified TaskTracker and related classes so that per-job local data on the TaskTracker node has right access-control. Important changes:
 - All files/directories of the job on the TaskTracker are now user-owned by the job-owner and group-owner by a special TaskTracker's group.
 - The permissions of the file/directories are set to the most restrictive permissions possible.
 - Files/dirs shareable by all tasks of the job on this TT are set proper access control as soon as possible, i.e immediately after job-localization and those that are private to a single task are set access control after the corresponding task's localization.
 - Also fixes MAPREDUCE-131 which is related to a bug because of which tasks hang when the taskcontroller.cfg has multiple entries for mapred.local.dir
 - A new configuration entry hadoop.log.dir corresponding to the hadoop.log.dir in TT's configuration is now needed in task-controller.cfg so as to support restricted access control for userlogs of the tasks on the TaskTracker.

• Assignee: Vinod Kumar Vavilapalli
• Reporter: Arun Murthy
• Created: 22/Oct/08 20:27
• Updated: 06/Jan/11 09:37
• Resolved: 12/Aug/09 16:21

Issue Links

• duplicates: MAPREDUCE-131 After HADOOP-5420, tasks hang when the taskcontroller.cfg has multiple entries for mapred.local.dir
• relates to: MAPREDUCE-720 Task logs should have right access-control
• relates to: MAPREDUCE-2238 Undeletable build directories