Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 26 Jun 2012 00:49:44 +0000 (UTC)
From: "Bikas Saha (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1815982012.54422.1340671784206.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Created] (HDFS-3565) Fix streaming job failures with
 WindowsResourceCalculatorPlugin
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Bikas Saha created HDFS-3565:
--------------------------------

             Summary: Fix streaming job failures with WindowsResourceCalculatorPlugin
                 Key: HDFS-3565
                 URL: https://issues.apache.org/jira/browse/HDFS-3565
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Bikas Saha
            Assignee: Bikas Saha


Some streaming jobs use local mode job runs that do not start tasks trackers. In these cases, the jvm context is not setup and hence local mode execution causes the code to crash.
Fix is to not not use ResourceCalculatorPlugin in such cases or make the local job run creating dummy jvm contexts. Choosing the first option because thats the current implicit behavior in Linux. The ProcfsBasedProcessTree (used inside the LinuxResourceCalculatorPlugin) does no real work when the process pid is not setup correctly. This is what happens when local job mode runs.


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