You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-user@hadoop.apache.org by Juan Martin Pampliega <jp...@gmail.com> on 2013/11/28 15:07:11 UTC

MRV2 job takes to long to start

Hi,

I have a map-reduce job that was developed for MRV1 and is now being run
daily with no modifications in a hadoop 2.2 cluster with MRV2.

For the first week at least the job worked as expected but now some days
the job takes a long time to start (like 30-50 minutes). The job starts a
large number of mappers (around 525) and it usually just took a couple of
minutes for it to start. Also, there are no other jobs running at the same
time.

Any ideas what might be causing this?

Thanks,
Juan.

Re: MRV2 job takes to long to start

Posted by Sandy Ryza <sa...@cloudera.com>.
What scheduler are you using?  What do you mean by "start"?  For the first
map task to start?

-Sandy


On Thu, Nov 28, 2013 at 6:07 AM, Juan Martin Pampliega <jpampliega@gmail.com
> wrote:

> Hi,
>
> I have a map-reduce job that was developed for MRV1 and is now being run
> daily with no modifications in a hadoop 2.2 cluster with MRV2.
>
> For the first week at least the job worked as expected but now some days
> the job takes a long time to start (like 30-50 minutes). The job starts a
> large number of mappers (around 525) and it usually just took a couple of
> minutes for it to start. Also, there are no other jobs running at the same
> time.
>
> Any ideas what might be causing this?
>
> Thanks,
> Juan.
>

Re: MRV2 job takes to long to start

Posted by Sandy Ryza <sa...@cloudera.com>.
What scheduler are you using?  What do you mean by "start"?  For the first
map task to start?

-Sandy


On Thu, Nov 28, 2013 at 6:07 AM, Juan Martin Pampliega <jpampliega@gmail.com
> wrote:

> Hi,
>
> I have a map-reduce job that was developed for MRV1 and is now being run
> daily with no modifications in a hadoop 2.2 cluster with MRV2.
>
> For the first week at least the job worked as expected but now some days
> the job takes a long time to start (like 30-50 minutes). The job starts a
> large number of mappers (around 525) and it usually just took a couple of
> minutes for it to start. Also, there are no other jobs running at the same
> time.
>
> Any ideas what might be causing this?
>
> Thanks,
> Juan.
>

Re: MRV2 job takes to long to start

Posted by Sandy Ryza <sa...@cloudera.com>.
What scheduler are you using?  What do you mean by "start"?  For the first
map task to start?

-Sandy


On Thu, Nov 28, 2013 at 6:07 AM, Juan Martin Pampliega <jpampliega@gmail.com
> wrote:

> Hi,
>
> I have a map-reduce job that was developed for MRV1 and is now being run
> daily with no modifications in a hadoop 2.2 cluster with MRV2.
>
> For the first week at least the job worked as expected but now some days
> the job takes a long time to start (like 30-50 minutes). The job starts a
> large number of mappers (around 525) and it usually just took a couple of
> minutes for it to start. Also, there are no other jobs running at the same
> time.
>
> Any ideas what might be causing this?
>
> Thanks,
> Juan.
>

Re: MRV2 job takes to long to start

Posted by Sandy Ryza <sa...@cloudera.com>.
What scheduler are you using?  What do you mean by "start"?  For the first
map task to start?

-Sandy


On Thu, Nov 28, 2013 at 6:07 AM, Juan Martin Pampliega <jpampliega@gmail.com
> wrote:

> Hi,
>
> I have a map-reduce job that was developed for MRV1 and is now being run
> daily with no modifications in a hadoop 2.2 cluster with MRV2.
>
> For the first week at least the job worked as expected but now some days
> the job takes a long time to start (like 30-50 minutes). The job starts a
> large number of mappers (around 525) and it usually just took a couple of
> minutes for it to start. Also, there are no other jobs running at the same
> time.
>
> Any ideas what might be causing this?
>
> Thanks,
> Juan.
>