hadoop-mapreduce-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shumin Guo <gsmst...@gmail.com>
Subject Re: Stuck Job - how should I troubleshoot?
Date Wed, 23 Apr 2014 03:02:16 GMT
As the last map task is in pending state, it is possible that some issue is
happening within your cluster, for example, not enough memory, deadlock,
data problem etc. You can kill this map task manually, and see if the
problem can be solved.


On Sun, Apr 20, 2014 at 9:46 AM, Serge Blazhievsky <hadoop.ca@gmail.com>wrote:

> It could be a case that some step of the job takes particularly long. Take
> a look at counters. If they are changing, job is not stuck just takes long
> time.
>
> Once you know that you could either debug deadlock or apply optimization
> techniques
>
>
> Serge
>
> Sent from my iPhone
>
> On Apr 20, 2014, at 4:12, Clay McDonald <stuart.mcdonald@bateswhite.com>
> wrote:
>
>  Hello all. Please see the attached screenshot. I have a job that is
> stuck. I’ve looked in logs but don’t see anything that jumps out at me. How
> should I trouble shoot this? Thanks, Clay
>
> <stuck_mapreduce_job.jpg>
>
>

Mime
View raw message