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 Clay McDonald <st...@bateswhite.com> on 2014/04/20 13:12:42 UTC
Stuck Job - how should I troubleshoot?
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
Re: Stuck Job - how should I troubleshoot?
Posted by Shumin Guo <gs...@gmail.com>.
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 <ha...@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 <st...@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>
>
>
Re: Stuck Job - how should I troubleshoot?
Posted by Shumin Guo <gs...@gmail.com>.
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 <ha...@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 <st...@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>
>
>
Re: Stuck Job - how should I troubleshoot?
Posted by Shumin Guo <gs...@gmail.com>.
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 <ha...@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 <st...@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>
>
>
Re: Stuck Job - how should I troubleshoot?
Posted by Shumin Guo <gs...@gmail.com>.
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 <ha...@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 <st...@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>
>
>
Re: Stuck Job - how should I troubleshoot?
Posted by Serge Blazhievsky <ha...@gmail.com>.
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 <st...@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>
Re: Stuck Job - how should I troubleshoot?
Posted by Serge Blazhievsky <ha...@gmail.com>.
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 <st...@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>
Re: Stuck Job - how should I troubleshoot?
Posted by Serge Blazhievsky <ha...@gmail.com>.
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 <st...@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>
Re: Stuck Job - how should I troubleshoot?
Posted by Serge Blazhievsky <ha...@gmail.com>.
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 <st...@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>