hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3426) uber-jobs tried to write outputs into wrong dir
Date Mon, 12 Dec 2011 23:33:30 GMT

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

Vinod Kumar Vavilapalli commented on MAPREDUCE-3426:

Mostly looks good. Minor comments on the patch.
 - Jobimpl changes: Not this patch's fault, duplicate comment starting "User has overall veto
power over uberization"
 - RMCommunicator.stop() is still not thread-safe/idempotent - the shutdown hook and the stop-event
handling may both find the volatile boolean be true and proceed. This method needs synchronization.
 - JobStatus constructors - in both mapred and map reduce classes - need to backwards compatible.
> uber-jobs tried to write outputs into wrong dir
> -----------------------------------------------
>                 Key: MAPREDUCE-3426
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3426
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: mrv2
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Hitesh Shah
>             Fix For: 0.23.1
>         Attachments: MR-3426.1.patch, MR-3426.2.patch
> Incorrect setup of the uber tasks causes tasks to try to write intermidiate outputs into
dirs that the user does not have permissions to write to on a secure cluster. 

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