hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2847) [HOD] Idle cluster cleanup does not work if the JobTracker becomes unresponsive to RPC calls
Date Fri, 29 Feb 2008 10:56:51 GMT

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

Vinod Kumar Vavilapalli commented on HADOOP-2847:
-------------------------------------------------

+1 . Patch looks good. Tested both by ordinary idle cluster timeout and by stopping the jobtracker
explicitly by a stop signal; both allocations get deallocated after crossing idleness-limit.

> [HOD] Idle cluster cleanup does not work if the JobTracker becomes unresponsive to RPC
calls
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2847
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2847
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/hod
>    Affects Versions: 0.16.0
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
>            Priority: Blocker
>             Fix For: 0.16.1
>
>         Attachments: hadoop-2847
>
>
> In some erroneous conditions, the Hadoop JobTracker becomes unresponsive to RPC calls
(for e.g. if a misconfiguration causes the JobTracker to run out of memory). In such cases,
a cluster allocated by HOD no longer runs any jobs and is wastefully holding up nodes. The
usual idle cluster cleaner should deallocate the cluster ideally, but it does not.

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