You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Satish Subhashrao Saley (JIRA)" <ji...@apache.org> on 2016/08/17 16:42:21 UTC
[jira] [Commented] (OOZIE-2641) rerunning an oozie coordinator job
stucks on waiting
[ https://issues.apache.org/jira/browse/OOZIE-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424866#comment-15424866 ]
Satish Subhashrao Saley commented on OOZIE-2641:
------------------------------------------------
Solution is to update the last modified time only when we update the coord action.
> rerunning an oozie coordinator job stucks on waiting
> ----------------------------------------------------
>
> Key: OOZIE-2641
> URL: https://issues.apache.org/jira/browse/OOZIE-2641
> Project: Oozie
> Issue Type: Bug
> Reporter: Satish Subhashrao Saley
> Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2641-1.patch
>
>
> Suppose -
> Coord has two dependencies
> 1. hcat://localhost:9083/digits/monthly_spaceid/date=20150801, which is push.
> 2. coord:latest(0) which is pull and its unresolved.
> User killed the coord and then rerun .
> If CoordPushDependencyCheckXCommand command is lost from queue and there is a coordInputCheckCommand command,
> RecoveryService will never recover CoordPushDependencyCheckXCommand because coordInputCheckCommand will keep on updating last modified time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)