Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <27748975.1158356003762.JavaMail.jira@brutus>
Date: Fri, 15 Sep 2006 14:33:23 -0700 (PDT)
From: "Michel Tourn (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Created: (HADOOP-540) Streaming should send keep-alive
 signals to Reporter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Streaming should send keep-alive signals to Reporter
----------------------------------------------------

                 Key: HADOOP-540
                 URL: http://issues.apache.org/jira/browse/HADOOP-540
             Project: Hadoop
          Issue Type: Bug
          Components: contrib/streaming
            Reporter: Michel Tourn


The goal is to avoid the 10-minutes Task timeout with certain usages of hadoopStreaming.

This proposal does not introduce an artificial keep-alive heartbeat: 
it still requires the external Application to have activity.

Streaming should set Reporter status in more places:

1. output to side-effect files should (periodically) set reporter status.

2. Application's stderr data should (periodically) set reporter status.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira