Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1971819639.1217023294864.JavaMail.jira@brutus>
Date: Fri, 25 Jul 2008 15:01:34 -0700 (PDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Created: (HADOOP-3837) hadop streaming does not use progress
 reporting to detect hung tasks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

hadop streaming does not use progress reporting to detect hung tasks
--------------------------------------------------------------------

                 Key: HADOOP-3837
                 URL: https://issues.apache.org/jira/browse/HADOOP-3837
             Project: Hadoop Core
          Issue Type: Bug
          Components: contrib/streaming
    Affects Versions: 0.17.0
            Reporter: dhruba borthakur


Hadoop streaming (StreamJob.java) sets mapred.task.timeout to 0. This effectively means that if tasks hang (either due to bad user code or machine related issue), these tasks never encounters a timeout. This causes the entire job to hang.

I propose that hadoop streaming not set the timeout to 0. By default, the settings in hadoop-default.xml should be effective for streaming jobs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.