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

Posted to dev@oozie.apache.org by "Purshotam Shah (JIRA)" <ji...@apache.org> on 2014/08/21 00:55:30 UTC

[jira] [Commented] (OOZIE-1819) Avoid early queueing of CoordActionInputCheckXCommand

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

Purshotam Shah commented on OOZIE-1819:
---------------------------------------

One area we didn't cover is recovery service.
Even if avoid early queueing of CoordActionInputCheckXCommand from CoordMaterializeTransitionXCommand, recovery service will keep on requeuing it.

RecoveryService should only pick waiting coord action whose nominal time <=current time.

> Avoid early queueing of CoordActionInputCheckXCommand
> -----------------------------------------------------
>
>                 Key: OOZIE-1819
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1819
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Shwetha G S
>            Assignee: Shwetha G S
>             Fix For: 4.1.0
>
>         Attachments: OOZIE-1819-v2.patch, OOZIE-1819-v3.patch, OOZIE-1819.patch, OOZIE-1819.patch, OOZIE-1819.patch
>
>
> Currently, when coord action is materialised, CoordActionInputCheckXCommand is queued immediately. If the action is materialised long before the nominal time, this unnecessarily keeps executing CoordActionInputCheckXCommand and re-queues till nominal time. Instead,  CoordActionInputCheckXCommand can be queued with delay = (nominal time - now)



--
This message was sent by Atlassian JIRA
(v6.2#6252)