[
https://issues.apache.org/jira/browse/HADOOP-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley updated HADOOP-4161:
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.19.0)
Status: Resolved (was: Patch Available)
I just committed this to trunk and branch-0.18. Thanks Vinod!
> [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
>
> 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.
