[
https://issues.apache.org/jira/browse/MAPREDUCE-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444189#comment-13444189
]
Aaron T. Myers commented on MAPREDUCE-2374:
-------------------------------------------
bq. ATM - In future, please open a separate YARN jira. It's very odd to have
MAPREDUCE jira numbers in hadoop-yarn-project/CHANGES.txt.
Sorry, Arun. I didn't quite know what to do with this since this JIRA was
opened long before YARN was split off from MR. When committing, I also noticed
that there is some precedent for having a MAPREDUCE JIRA entry in the YARN
CHANGES.txt (MAPREDUCE-4323) and so thought it was OK. I agree that putting a
MAPREDUCE jira in the YARN CHANGES.txt is odd, but opening a separate JIRA just
so we have a new number for putting in CHANGES.txt also seemed odd to me. Doing
so would also serve to artificially separate the issues from the branch-1 and
branch-0.23 fixes, which seemed less than ideal as well. Anyway, my point is
just that the right thing to do was not obvious.
> "Text File Busy" errors launching MR tasks
> ------------------------------------------
>
> 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: Andy Isaacson
> Fix For: 1.2.0, 0.23.3, 2.2.0-alpha
>
> Attachments: failed_taskjvmsh.strace, mapreduce-2374-2.txt,
> mapreduce-2374-branch-1.patch, mapreduce-2374-on-20sec.txt,
> mapreduce-2374.txt, mapreduce-2374.txt, mapreduce-2374.txt,
> successfull_taskjvmsh.strace
>
>
> Some very small percentage of tasks fail with a "Text file busy" error.
> The following was the original diagnosis:
> {quote}
> 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.
> {quote}
> .. but turned out to be another issue as well (see below)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
