You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Viraj Bhat (JIRA)" <ji...@apache.org> on 2008/10/08 03:49:44 UTC

[jira] Updated: (HADOOP-4352) a job stays in running state forever, even though all the tasks completed a long time ago

     [ https://issues.apache.org/jira/browse/HADOOP-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Viraj Bhat updated HADOOP-4352:
-------------------------------

    Attachment: jobtracker_jstatck_trace.out

Java Stack trace for the JobTracker process

> a job stays in running state forever, even though all the tasks completed a long time ago
> -----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4352
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4352
>             Project: Hadoop Core
>          Issue Type: Bug
>    Affects Versions: 0.17.2
>            Reporter: Runping Qi
>         Attachments: jobtracker_jstatck_trace.out
>
>
> I encountered a job  that stays in running state forever, even though all the tasks completed a long time ago.
> The last lines in the job tracker log complain that it cannot connect to the namenode of the dfs, although the dfs namenode works fine at present time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.