hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4161) [HOD] Uncaught exceptions can potentially hang hod-client.
Date Thu, 11 Sep 2008 14:51:45 GMT

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

Hemanth Yamijala commented on HADOOP-4161:
------------------------------------------

Patch looks good. +1

> [HOD] Uncaught exceptions can potentially hang hod-client.
> ----------------------------------------------------------
>
>                 Key: HADOOP-4161
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4161
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/hod
>            Reporter: Vinod K V
>            Assignee: Vinod K V
>             Fix For: 0.18.1, 0.19.0
>
>         Attachments: HADOOP-4161
>
>
> In hod-client, we have
> {code}
> sys.exit(hod.operation())
> sys.exit(hod.script())
> {code}
> sys.exit(opCode) makes sure that the client is truly cleaned up, killing unjoined threads
etc. So, exceptions not caught by hodRunner.operation() or hodRunner.script(), will by-pass
sys.exit method and thus can potentially hang hod-client.
> For e.g., when hod allocate fails after allocation and before service-registry thread
is cleaned up, hod client will hang.

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