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

Andy Isaacson commented on MAPREDUCE-2374:
------------------------------------------

bq. I have noticed ENOEXEC errors for both successful as well as unsuccessful 
(ETXTBSY) cases of bash -c /path/to/taskjvm.sh calls through strace output. So 
I am not sure if this is the root cause. However, it doesn't hurts to add the 
#!/bin/sh construct. 

If you have strace output showing the ETXTBSY, could you upload it to the bug?  
That would greatly help in isolating the problem.  Especially if it also shows 
the open()/write()/close() of the script file.  Specific kernel version where 
the problem has been seen would be great too!
                
> Should not use PrintWriter to write taskjvm.sh
> ----------------------------------------------
>
>                 Key: MAPREDUCE-2374
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2374
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.22.1
>
>         Attachments: mapreduce-2374-on-20sec.txt, mapreduce-2374.txt, 
> mapreduce-2374.txt
>
>
> Our use of PrintWriter in TaskController.writeCommand is unsafe, since that 
> class swallows all IO exceptions. We're not currently checking for errors, 
> which I'm seeing result in occasional task failures with the message "Text 
> file busy" - assumedly because the close() call is failing silently for some 
> reason.

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

        

Reply via email to