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:
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 wrot
