-Re: Jobs are still in running state after executing "hadoop job -kill jobId"
Edward Capriolo 2011-07-05, 14:50
On Tue, Jul 5, 2011 at 10:05 AM, <[EMAIL PROTECTED]> wrote:
> Um kill -9 "pid" ?
> -----Original Message-----
> From: Juwei Shi [mailto:[EMAIL PROTECTED]]
> Sent: Friday, July 01, 2011 10:53 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Jobs are still in running state after executing "hadoop job
> -kill jobId"
> I faced a problem that the jobs are still running after executing
> job -kill jobId". I rebooted the cluster but the job still can not be
> The hadoop version is 0.20.2.
> Any idea?
> Thanks in advance!
> - Juwei
This happens sometimes. A task gets orphaned from the Task Tracker and never
goes away. It is a good idea to have a nagios check for very old tasks
because the orphans slowly such your memory away especially if the task
launches with a big Xmx. You really *should not* need to be nuking tasks
like this but occasionally it happens.