[
https://issues.apache.org/jira/browse/OOZIE-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281893#comment-14281893
]
Jaydeep Vishwakarma commented on OOZIE-1222:
--------------------------------------------
[~szzhu], I think your most of the concerns related to rerun have been taken
care in following jira.
https://issues.apache.org/jira/browse/OOZIE-1536
Please add the sub task there if anything additional you want to add.
> Improve OOZIE Coordinator Action rerun
> --------------------------------------
>
> Key: OOZIE-1222
> URL: https://issues.apache.org/jira/browse/OOZIE-1222
> Project: Oozie
> Issue Type: Improvement
> Components: coordinator
> Affects Versions: 3.2.0
> Reporter: Shanzhong Zhu
>
> Current rerunning a coordinator action resets its external id (which maps to
> workflow job) and external status. This means it will run a fresh workflow
> job which explains why the client method getRerun() was returning '0'.
> Can we enhance the coordinator rerun to be consistent with the workflow rerun?
> * Keep the same workflow ID.
> * Support rerun from beginning or rerun from the failed WF action (Right now
> rerun a coordinator action always rerunning from beginning).
> * Rerun count (getReRun() ) reflects the number of tries. (Rignt now, it's
> always returning 0).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
