Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 30 Aug 2012 03:58:09 +1100 (NCT)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <655840300.12599.1346259489519.JavaMail.jiratomcat@arcas>
Subject: [jira] [Moved] (YARN-59) "Text File Busy" errors launching MR tasks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun C Murthy moved MAPREDUCE-4605 to YARN-59:
----------------------------------------------

        Fix Version/s:     (was: 2.2.0-alpha)
                           (was: 1.2.0)
                           (was: 0.23.3)
                       0.23.3
                       2.2.0-alpha
             Assignee:     (was: Andy Isaacson)
    Affects Version/s:     (was: 0.22.0)
         Hadoop Flags:   (was: Reviewed)
                  Key: YARN-59  (was: MAPREDUCE-4605)
              Project: Hadoop YARN  (was: Hadoop Map/Reduce)
    
> "Text File Busy" errors launching MR tasks
> ------------------------------------------
>
>                 Key: YARN-59
>                 URL: https://issues.apache.org/jira/browse/YARN-59
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Todd Lipcon
>             Fix For: 2.2.0-alpha, 0.23.3
>
>
> 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