[
https://issues.apache.org/jira/browse/OOZIE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072534#comment-14072534
]
Purshotam Shah commented on OOZIE-1536:
---------------------------------------
{quote}
CoordActionInputCheck and further commands on coord action pick the coord xml
from COORD_ACTIONS table, but coord update updates COORD_JOBS table. This means
coord update is effective for the new actions to be materialised and not the
already materialised ones. The re-runs that we are talking about are on the
already completed actions which means they are already materialised and there
is no way of changing the definition of these by coord update. Isn't it?
{quote}
Coord rerun with refresh option will run coord action with updated coord
definition.
{quote}
Earlier, when workflow state changed, the corresponding coord action status
change was queued. So, there was delay in propagating the status. So, there
were instances when workflow was in running state, but coord action in killed
state(because of wf re-run). So, coord action re-run in this case would launch
another workflow.
{quote}
Then it's a different issue, making kill command as synchronous will solve the
issue.
> 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)
