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/03/13 17:47:43 UTC

[jira] [Commented] (OOZIE-1742) CoordChangeXCommand doesn't update LastModifiedTime properly

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

purshotam shah commented on OOZIE-1742:
---------------------------------------


This is similar to OOZIE-1718 and [~chitnis] has already put patch for review.
OOZIE-1718 : Coord Job Query UPDATE_COORD_JOB_CHANGE does not persist last modified time

> CoordChangeXCommand doesn't update LastModifiedTime properly
> ------------------------------------------------------------
>
>                 Key: OOZIE-1742
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1742
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Ryota Egashira
>            Assignee: Ryota Egashira
>         Attachments: OOZIE-1742.patch
>
>
> This issue manifested as coordinator jobs getting stuck in running state even after end-time passes. This situation happens after endtime of Coordinator job is changed (by CoordJobChange) when coordinator is already done with materialization and it's coord actions have been succeeded.



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