hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Foley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2374) "Text File Busy" errors launching MR tasks
Date Wed, 28 Nov 2012 22:58:00 GMT

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

Matt Foley commented on MAPREDUCE-2374:
---------------------------------------

Marc, being in branch-1, it will be in 1.2.0 when we make that release in December.
Andy, please go ahead and commit it to branch-1.1 also, so it will be in 1.1.2 when that patch
release is made.
Marc, you can request it be committed to branch-1.0 also, but at this time there are no plans
to produce a 1.0.5 release.  Are you able to move to 1.1.1 instead?  1.1.1 passed vote yesterday,
and I will have it published and announced in the next day or two.
                
> "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: 0.23.3, 2.0.2-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

Mime
View raw message