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

Hemanth Yamijala commented on MAPREDUCE-1415:
---------------------------------------------

Looking at one of the failed tests, it appears that we have test cases that use 
default commands like 'xargs' as the mapper, but don't specify the full path. 
Hence the code tries to set permissions for it in the current working directory 
and fails (because the file does not exist). I thought FileUtil.fullyDelete 
actually throws an exception if there's a command failure, but I see in code 
that we actually ignore exceptions explicitly. I assume the failure should have 
been seen before as well - at some debug log level. 

So, one option could be to not check the return code of setPermissions. Another 
option is to change the tests to work with full paths. However, this is 
inherently system dependent (as xargs could potentially be under multiple 
directories depending on the system).

> With streaming jobs and LinuxTaskController, the localized streaming binary 
> has 571 permissions instead of 570
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1415
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1415
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/streaming, security
>            Reporter: Vinod K V
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 0.22.0
>
>         Attachments: patch-1415-1.txt, patch-1415-2.txt, patch-1415.txt
>
>
> After MAPREDUCE-856, all localized files are expected to have **0 permissions 
> for the sake of security.
> This was found by Karam while testing LinuxTaskController functionality after 
> MAPREDUCE-856.

-- 
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