[
https://issues.apache.org/jira/browse/OOZIE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130257#comment-14130257
]
Rohini Palaniswamy commented on OOZIE-1536:
-------------------------------------------
[~shwethags],
We would still prefer having one new workflow for coord action reruns for
maintaining history/change log which is very useful and important as well for
us and our users. Even yesterday there was a user reported problem and we had
to look at the previous coord action reruns to determine the issue. This has
happened a lot of times for us and we did add the "Coord Action Reruns" tab
specifically for this purpose to easily get the list of reruns. In fact, we
have asks to show the older runs in the workflow page itself in addition to the
"Coord Action Reruns" page as that will be more easy. With the current
behavior, if needed we can easily add checks to not allow rerun of the workflow
if another workflow from that coord action is running to avoid the issues you
are seeing. We can also totally not allow rerunning the workflow directly at
all if coord is a parent, but if they want to quickly rerun and do skip-nodes
to meet SLA, that will prevent users from doing it.
If putting safe guards in the existing behavior does not work for you, then
we can explore possibilities of having both behaviors available and make that
configurable as a server side option.
> Coordinator action reruns start a new workflow
> ----------------------------------------------
>
> Key: OOZIE-1536
> URL: https://issues.apache.org/jira/browse/OOZIE-1536
> Project: Oozie
> Issue Type: Improvement
> Reporter: Srikanth Sundarrajan
>
> Coordinator action reruns start a new workflow and if existing workflow for
> the action is in running state, the same is not checked. Coord rerun can
> possibly do a workflow re-run to prevent this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
