Re: Map Task timed out?
Thanks for all advices. :)
Edward
On Fri, Jun 13, 2008 at 3:22 PM, lohit <[EMAIL PROTECTED]> wrote:
> Check RandomWriter.java
> look for reporter.setStatus("wrote record " + itemCount + "..
>
> - Original Message
> From: Edward J. Yoon <[EMAIL PROTECTED]>
> To: core-user@hadoop.apache.org
> Sent: Thursday, June 12, 2008 10:35:14 PM
> Subject: Re: Map Task timed out?
>
> Thanks for your nice answer. :)
> Then, Can I handle the *reporter*? If so, please give me some examples.
>
> Thanks.
>
> On Fri, Jun 13, 2008 at 2:18 PM, lohit <[EMAIL PROTECTED]> wrote:
>> Yes, there is a timeout defined by mapred.task.timeout
>> default was 600 seconds. And here silent means the task (either map or
>> reduce ) has not reported any status using the reporter you get with
>> map/reduce function
>>
>> Thanks,
>> Lohit
>>
>> - Original Message
>> From: Edward J. Yoon <[EMAIL PROTECTED]>
>> To: core-user@hadoop.apache.org
>> Sent: Thursday, June 12, 2008 7:12:50 PM
>> Subject: Map Task timed out?
>>
>> Hi,
>>
>> If map task is unexpectedly "silent" for a long time (e.g. wait for
>> other application response), What happen? Is there any limit for
>> staying?
>>
>> Thanks
>> --
>> Best regards,
>> Edward J. Yoon,
>> http://blog.udanax.org
>>
>>
>
>
>
> --
> Best regards,
> Edward J. Yoon,
> http://blog.udanax.org
>
>
--
Best regards,
Edward J. Yoon,
http://blog.udanax.org
Re: Map Task timed out?
Check RandomWriter.java
look for reporter.setStatus("wrote record " + itemCount + "..
- Original Message
From: Edward J. Yoon <[EMAIL PROTECTED]>
To: core-user@hadoop.apache.org
Sent: Thursday, June 12, 2008 10:35:14 PM
Subject: Re: Map Task timed out?
Thanks for your nice answer. :)
Then, Can I handle the *reporter*? If so, please give me some examples.
Thanks.
On Fri, Jun 13, 2008 at 2:18 PM, lohit <[EMAIL PROTECTED]> wrote:
> Yes, there is a timeout defined by mapred.task.timeout
> default was 600 seconds. And here silent means the task (either map or reduce
> ) has not reported any status using the reporter you get with map/reduce
> function
>
> Thanks,
> Lohit
>
> - Original Message
> From: Edward J. Yoon <[EMAIL PROTECTED]>
> To: core-user@hadoop.apache.org
> Sent: Thursday, June 12, 2008 7:12:50 PM
> Subject: Map Task timed out?
>
> Hi,
>
> If map task is unexpectedly "silent" for a long time (e.g. wait for
> other application response), What happen? Is there any limit for
> staying?
>
> Thanks
> --
> Best regards,
> Edward J. Yoon,
> http://blog.udanax.org
>
>
--
Best regards,
Edward J. Yoon,
http://blog.udanax.org
Re: Map Task timed out?
Edward J. Yoon wrote: Thanks for your nice answer. :) Then, Can I handle the *reporter*? If so, please give me some examples. Edward, you can always spawn a thread that will periodically call reporter.progress() and then wait for the (remote/blocking) call to complete. Once the call is complete simply destroy this thread. Hope that helps. Amar Thanks. On Fri, Jun 13, 2008 at 2:18 PM, lohit <[EMAIL PROTECTED]> wrote: Yes, there is a timeout defined by mapred.task.timeout default was 600 seconds. And here silent means the task (either map or reduce ) has not reported any status using the reporter you get with map/reduce function Thanks, Lohit - Original Message From: Edward J. Yoon <[EMAIL PROTECTED]> To: core-user@hadoop.apache.org Sent: Thursday, June 12, 2008 7:12:50 PM Subject: Map Task timed out? Hi, If map task is unexpectedly "silent" for a long time (e.g. wait for other application response), What happen? Is there any limit for staying? Thanks -- Best regards, Edward J. Yoon, http://blog.udanax.org
Re: Map Task timed out?
Thanks for your nice answer. :) Then, Can I handle the *reporter*? If so, please give me some examples. Thanks. On Fri, Jun 13, 2008 at 2:18 PM, lohit <[EMAIL PROTECTED]> wrote: > Yes, there is a timeout defined by mapred.task.timeout > default was 600 seconds. And here silent means the task (either map or reduce > ) has not reported any status using the reporter you get with map/reduce > function > > Thanks, > Lohit > > - Original Message > From: Edward J. Yoon <[EMAIL PROTECTED]> > To: core-user@hadoop.apache.org > Sent: Thursday, June 12, 2008 7:12:50 PM > Subject: Map Task timed out? > > Hi, > > If map task is unexpectedly "silent" for a long time (e.g. wait for > other application response), What happen? Is there any limit for > staying? > > Thanks > -- > Best regards, > Edward J. Yoon, > http://blog.udanax.org > > -- Best regards, Edward J. Yoon, http://blog.udanax.org
Re: Map Task timed out?
Yes, there is a timeout defined by mapred.task.timeout default was 600 seconds. And here silent means the task (either map or reduce ) has not reported any status using the reporter you get with map/reduce function Thanks, Lohit - Original Message From: Edward J. Yoon <[EMAIL PROTECTED]> To: core-user@hadoop.apache.org Sent: Thursday, June 12, 2008 7:12:50 PM Subject: Map Task timed out? Hi, If map task is unexpectedly "silent" for a long time (e.g. wait for other application response), What happen? Is there any limit for staying? Thanks -- Best regards, Edward J. Yoon, http://blog.udanax.org
Map Task timed out?
Hi, If map task is unexpectedly "silent" for a long time (e.g. wait for other application response), What happen? Is there any limit for staying? Thanks -- Best regards, Edward J. Yoon, http://blog.udanax.org
