You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Shanzhong Zhu (JIRA)" <ji...@apache.org> on 2013/07/05 08:23:49 UTC
[jira] [Commented] (OOZIE-1222) Improve OOZIE Coordinator Action
rerun
[ https://issues.apache.org/jira/browse/OOZIE-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700475#comment-13700475 ]
Shanzhong Zhu commented on OOZIE-1222:
--------------------------------------
Do we have any plan to implement this feature?
Thanks,
Shanzhong
> 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 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