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

Vinod K V updated MAPREDUCE-1607:
---------------------------------

    Release Note: Fixed initialization of a task-cleanup attempt's log 
directory by setting correct permissions via task-controller. Added new log4j 
properties hadoop.tasklog.iscleanup and log4j.appender.TLA.isCleanup to 
conf/log4j.properties. Changed the userlogs for a task-cleanup attempt to go 
into its own directory instead of the original attempt directory. This is an 
incompatible change as old userlogs of cleanup attempt-dirs before this release 
will no longer be visible.   (was: Fixed initialization of a task-cleanup 
attempt's log directory by setting correct permissions via task-controller. 
Changed the userlogs for a task-cleanup attempt to go into its own directory 
instead of the original attempt directory. This is an incompatible change as 
old userlogs of cleanup attempt-dirs will no longer be visible.)

> Task controller may not set permissions for a task cleanup attempt's log 
> directory
> ----------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1607
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1607
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: task-controller
>    Affects Versions: 0.21.0
>            Reporter: Hemanth Yamijala
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 0.21.0
>
>         Attachments: patch-1607-1.txt, patch-1607-2.txt, 
> patch-1607-ydist.txt, patch-1607.txt
>
>
> Task controller uses the INITIALIZE_TASK command to initialize task attempt 
> and task log directories. For cleanup tasks, task attempt directories are 
> named as task-attempt-id.cleanup. But log directories do not have the 
> .cleanup suffix. The task controller is not aware of this distinction and 
> tries to set permissions for log directories named task-attempt-id.cleanup. 
> This is a NO-OP. Typically the task cleanup runs on the same node that ran 
> the original task attempt as well. So, the task log directories are already 
> properly initialized. However, the task cleanup can run on a node that has 
> not run the original task attempt. In that case, the initialization would not 
> happen and this could result in the cleanup task failing.

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

Reply via email to