You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Bowen Zhang (JIRA)" <ji...@apache.org> on 2013/08/27 02:23:51 UTC

[jira] [Commented] (OOZIE-1514) Rerunning a coordinator with no input dependencies puts actions in WAITING instead of READY and proceeding

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

Bowen Zhang commented on OOZIE-1514:
------------------------------------

[~chitnis], Can you or someone else take a look at the patch?
                
> Rerunning a coordinator with no input dependencies puts actions in WAITING instead of READY and proceeding
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-1514
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1514
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: 4.0.0
>            Reporter: Mona Chitnis
>            Assignee: Bowen Zhang
>            Priority: Blocker
>             Fix For: 4.0.0
>
>         Attachments: oozie-1514.patch
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Following issue reported by Bowen:
>  
> {quote}
> rerun oozie coordinator action that has no data dependency will make the action stuck in "WAITING" forever.
> The issue has to do with the change introduced in coordActionInputCheckXCommand. The rerun action will fail this if statement:
> if (!nonExistListStr.equals(missingDeps))
> since nonExistListStr and missingDeps are both empty strings. Once it fails the if statement, isChangeDependency is still
> set to false and the status change to "READY" will not be persisted since we will call CoordActionUpdateForModifiedTimeJPAExecutor instead of CoordActionUpdateForInputCheckJPAExecutor in the updateCoordAction method.
> the Action is in "WAITING" stage forever.
> {quote}

--
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