[
https://issues.apache.org/jira/browse/OOZIE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080398#comment-14080398
]
Purshotam Shah commented on OOZIE-1536:
---------------------------------------
{quote}
An initial run of the coord action creates a workflow and then a subsequent run
creates another workflow. It is understood that coord re-run will make sure
that the older workflow is not running before the second one starts. However It
appears like Workflow #1 can be run independently through a direct workflow
re-run (not going via coord re-run). In which case you might see both the
workflows run and the behavior is undefined.
If there was a one to one correspondence between a coord action and a workflow
this problem might not occur. Makes sense ?
{quote}
Yes, I forgot about that, rerunning of WF doesn't change coord action status.
IMO, while rerunning coord action we should also check WF status and if it's
running we should throw exception.
> 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)
