You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org> on 2014/02/18 07:08:19 UTC

[jira] [Commented] (OOZIE-1699) Some of the commands submitted to Oozie internal queue are never executed

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

Srikanth Sundarrajan commented on OOZIE-1699:
---------------------------------------------

Do find many uncaught exceptions from oozie captured in the catalina.out file.

{code}
>>> Exception in thread "pool-2-thread-22" java.lang.OutOfMemoryError: GC overhead limit exceeded
>>> Exception in thread "pool-2-thread-19" java.lang.IllegalMonitorStateException
   ...
           at org.apache.oozie.util.PollablePriorityDelayQueue.poll(PollablePriorityDelayQueue.java:80)
   ...
>>> Exception in thread "pool-2-thread-24" java.lang.IllegalStateException: queueElement already in a queue
            at org.apache.oozie.util.PriorityDelayQueue.offer(PriorityDelayQueue.java:347)
{code}

Looks like these threads have died and the ThreadPoolExecutor has created new threads to make good for these.

> Some of the commands submitted to Oozie internal queue are never executed
> -------------------------------------------------------------------------
>
>                 Key: OOZIE-1699
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1699
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Srikanth Sundarrajan
>            Assignee: Srikanth Sundarrajan
>
> At scale, we are seeing issues with some command submitted to the command queue in CallableQueueService aren't getting executed at all.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)