You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@sqoop.apache.org by "arvind@cloudera.com" <ar...@cloudera.com> on 2011/08/23 18:13:39 UTC
Re: [sqoop-user] significance of INFO mapred.Task: Task 'attempt_local_0001_m_000000_0'
[Moving the thread to sqoop-user@incubator.apache.org]
Sonal,
These are the specific attempts to execute the map task that are
configured for the job. If you point your browser to the job-tracker
web UI, you can drill down into the job IDs into the various job
attempt details and see the completed logs for each of these.
Arvind
On Tue, Aug 23, 2011 at 7:18 AM, Sonal <im...@gmail.com> wrote:
> Hi,
>
> Just want to ask, what is the significance of
> INFO mapred.Task: Task:attempt_local_0001_m_000000_0 is done. And is
> in the process of commiting
> 11/08/23 06:57:12 INFO mapred.LocalJobRunner:
> 11/08/23 06:57:12 INFO mapred.Task: Task
> 'attempt_local_0001_m_000000_0' done.
>
> with multiple task attempts of mapper like:
> Task:attempt_local_0001_m_000000_0 is done.
> Task:attempt_local_0001_m_000001_0 is done.
> Task:attempt_local_0001_m_000002_0 is done.
> Task:attempt_local_0001_m_000003_0 is done.
>
> What does these attempts mean?
>
> Thanks & Regards,
> Sonal Kumar
>
> --
> NOTE: The mailing list sqoop-user@cloudera.org is deprecated in favor of Apache Sqoop mailing list sqoop-user@incubator.apache.org. Please subscribe to it by sending an email to incubator-sqoop-user-subscribe@apache.org.
>
Re: [sqoop-user] Re: significance of INFO mapred.Task: Task 'attempt_local_0001_m_000000_0'
Posted by "arvind@cloudera.com" <ar...@cloudera.com>.
[Please subscribe and reply to sqoop-user@incubator.apache.org]
> Did you mean 1 map job took these many attempts to finish the job?
Typically, the job submitted by Sqoop has by default 4 map tasks
configured. When these tasks are executed, their attempt takes on the
form task_<unique_id>_m_00000[0-4]. Each of these tasks in turn have
attempts that are named attempt_<unique_id>_m_00000[0-4]_n, where n
represents the actual map execution attempt number.
In the output that you mentioned here, it seems that there were four
map tasks in the job, and each task made a single attempt that was
successful.
Thanks,
Arvind
On Tue, Aug 23, 2011 at 11:04 PM, Sonal <im...@gmail.com> wrote:
> Hi,
>
> Thanks for your reply.
> Did you mean 1 map job took these many attempts to finish the job?
>
> That means only one map job is currently active.
> Is it like in stand alone setup we can only have one map/reduce task
> to finish the job , even when we are specifying --num-mappers option?
>
> Thanks & Regards,
> Sonal Kumar
>
> On Aug 23, 9:13 pm, "arv...@cloudera.com" <ar...@cloudera.com> wrote:
>> [Moving the thread to sqoop-u...@incubator.apache.org]
>>
>> Sonal,
>>
>> These are the specific attempts to execute the map task that are
>> configured for the job. If you point your browser to the job-tracker
>> web UI, you can drill down into the job IDs into the various job
>> attempt details and see the completed logs for each of these.
>>
>> Arvind
>>
>> On Tue, Aug 23, 2011 at 7:18 AM, Sonal <im...@gmail.com> wrote:
>> > Hi,
>>
>> > Just want to ask, what is the significance of
>> > INFO mapred.Task: Task:attempt_local_0001_m_000000_0 is done. And is
>> > in the process of commiting
>> > 11/08/23 06:57:12 INFO mapred.LocalJobRunner:
>> > 11/08/23 06:57:12 INFO mapred.Task: Task
>> > 'attempt_local_0001_m_000000_0' done.
>>
>> > with multiple task attempts of mapper like:
>> > Task:attempt_local_0001_m_000000_0 is done.
>> > Task:attempt_local_0001_m_000001_0 is done.
>> > Task:attempt_local_0001_m_000002_0 is done.
>> > Task:attempt_local_0001_m_000003_0 is done.
>>
>> > What does these attempts mean?
>>
>> > Thanks & Regards,
>> > Sonal Kumar
>>
>> > --
>> > NOTE: The mailing list sqoop-u...@cloudera.org is deprecated in favor of Apache Sqoop mailing list sqoop-u...@incubator.apache.org. Please subscribe to it by sending an email to incubator-sqoop-user-subscr...@apache.org.
>
> --
> NOTE: The mailing list sqoop-user@cloudera.org is deprecated in favor of Apache Sqoop mailing list sqoop-user@incubator.apache.org. Please subscribe to it by sending an email to incubator-sqoop-user-subscribe@apache.org.
>