[
https://issues.apache.org/jira/browse/OOZIE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073807#comment-14073807
]
Purshotam Shah commented on OOZIE-1536:
---------------------------------------
{quote}
A coord is typically set-up to run a particular pipeline which consumes some
input, does some processing and generates some output. From user's perspective,
they look at the processing for each nominal time. It will be easier to monitor
and handle the pipeline if there is just one workflow per nominal time. (If
there are multiple workflows, users have to look at all of them to see what is
happening, monitor each one's state, handle parallel runs(which they have to
handle using external locking like zookeeper) etc). Even if the coord
definition is updated and there are new inputs and outputs and there is new
workflow path, workflow re-run can override all properties(including app path).
That way there is just one workflow per nominal time.
{quote}
We will never have two workflow running for a coord action. If two are running
then its a bug.
In your case two WF was running because of queue delay, and that it's the
actual issue. We should fix that rather then changing the coord rerun behavior.
There was also effort to display all rerun WF related to coord action.
https://issues.apache.org/jira/browse/OOZIE-1746
> 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.2#6252)
