Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-user@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns;
	h=mime-version:in-reply-to:references:content-type:message-id:
	content-transfer-encoding:from:subject:date:to:x-mailer;
	b=H0e8oNMdbnMJzEZI2o5/LQgDTUSGdX/LsEPfaTqE2TXZLY/hSfan3raGzyJ9QfLs
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <15153682.post@talk.nabble.com>
References: <898448.62794.qm@web57211.mail.re3.yahoo.com>
 <635575.71490.qm@web53610.mail.re2.yahoo.com> <15153682.post@talk.nabble.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A4C74939-F73D-4996-AA0D-D0921751A4EB@yahoo-inc.com>
Content-Transfer-Encoding: 7bit
From: Arun C Murthy <acm@yahoo-inc.com>
Subject: Re: Task was killed due to running over 600 sec
Date: Tue, 29 Jan 2008 07:03:30 -0800
To: core-user@hadoop.apache.org


On Jan 28, 2008, at 11:12 PM, ChaoChun Liang wrote:

>
>
> lohit.vijayarenu wrote:
>>
>> You could try setting the value of mapred.task.timeout to higher  
>> value.
>> Thanks,
>> Lohit
>>
>
> Could I set the different timeout values for the maper and reducer
> separately?
> In my case, the execution time for the mapper is short than the  
> reducer.
>

No. There isn't a way to do that.

However, it really _is_ better to send progress/status-updates to the  
TaskTracker rather than to work around it... infact it is as simple  
as calling *reporter.progress()* periodically, or reporter.setStatus  
on the reporter which is passed to the map/reduce method. It helps  
debugging too...

Arun
> Thanks.
> ChaoChun
>
> -- 
> View this message in context: http://www.nabble.com/Task-was-killed- 
> due-to-running-over-600-sec-tp15148129p15153682.html
> Sent from the Hadoop core-user mailing list archive at Nabble.com.
>