You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Virag Kothari (JIRA)" <ji...@apache.org> on 2013/06/27 07:10:22 UTC

[jira] [Commented] (OOZIE-1434) Commands not releasing memory lock

    [ https://issues.apache.org/jira/browse/OOZIE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694495#comment-13694495 ] 

Virag Kothari commented on OOZIE-1434:
--------------------------------------

[~tucu00], [~rkanter] As per our conversation in meetup, can you guys post your findings related to the MemoryLock implementation issue? 
                
> Commands not releasing memory lock
> ----------------------------------
>
>                 Key: OOZIE-1434
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1434
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Virag Kothari
>            Assignee: Virag Kothari
>
> If the command gets stuck in making a db call during loadState() after acquiring the lock, the lock will never be released and the job will be stuck forever. 
> Need to introduce a timeout for the database call.
> There might be also be an issue with the implementation of MemoryLocks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira