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

Posted to dev@oozie.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2013/08/23 16:04:51 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=13748557#comment-13748557 ] 

Rohini Palaniswamy commented on OOZIE-1434:
-------------------------------------------

Command was stuck fetching the blob from workflow jobs table. In this case it was a big workflow with 80 forked actions. 
https://forums.oracle.com/message/9524124#9524124

Haven't found a solution for this yet. 

The timeout in openjpa is only for time taken to execute the query. It does not involve time take to fetch the results. So that cannot be used to fix this issue.

http://openjpa.208410.n2.nabble.com/Timeout-for-fetching-data-td6954428.html
                
> 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