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 "Vinod K V (JIRA)" <ji...@apache.org> on 2008/09/11 11:33:44 UTC

[jira] Assigned: (HADOOP-4161) [HOD] Uncaught exceptions can potentially hang hod-client.

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

Vinod K V reassigned HADOOP-4161:
---------------------------------

    Assignee: Vinod K V

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