hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4352) a job stays in running state forever, even though all the tasks completed a long time ago
Date Tue, 07 Oct 2008 03:43:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637356#action_12637356
] 

Amareshwari Sriramadasu commented on HADOOP-4352:
-------------------------------------------------

Runping, Can you paste the lines from the JT log where it is complaining that it cannot to
namenode.  Is it in garbageCollect()?

> 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
>
> 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.


Mime
View raw message