[
https://issues.apache.org/jira/browse/MAPREDUCE-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420888#comment-13420888
]
Andy Isaacson commented on MAPREDUCE-2374:
------------------------------------------
bq. (I'll post another comment relevant to SElinux.)
There are some examples in the RHEL bugzilla of SElinux causing mysterious
ETXTBSY failures. Such failures should leave a trace in
{{/var/log/audit/audit.log}} on the node which experienced the failure.
Could someone who can reproduce this failure please check the audit log on the
node when a failure occurs? Even if you think that SElinux is turned off,
sometimes it's on by accident...
It would also potentially be helpful to compare an {{audit.log}} from a node
that runs the same code and does not experience the ETXTBSY failure.
> 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
>
>
> 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
