[
https://issues.apache.org/jira/browse/OOZIE-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118916#comment-14118916
]
Purshotam Shah commented on OOZIE-1581:
---------------------------------------
This is how the whole framework is.
If we rerun a coord from a completed bundle, bundle status doesn't change. To
change bundle status we have to rerun bundle with coord as param, then only
bundle status will change.
Same as with WF and coord action. If we rerun a WF, coord action status
shouldn't change.
And i think that is a correct behavior, rerunning of WF haven't triggered
rerunning of coord action. Running for coord action does lot of other things
beside submitting new WF like input dependency check, coord definition update (
if needed), delete output ( if needed). So it may not be correct to say coord
action has rerun if we rerun WF.
> Workflow performance optimizations
> ----------------------------------
>
> Key: OOZIE-1581
> URL: https://issues.apache.org/jira/browse/OOZIE-1581
> Project: Oozie
> Issue Type: Improvement
> Components: workflow
> Affects Versions: trunk
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Fix For: 4.1.0
>
> Attachments: OOZIE-1581-2.patch, OOZIE-1581-final.patch,
> OOZIE-1581-r6.patch, OOZIE-1581-r6.patch, OOZIE-1581-r7.patch,
> OOZIE-1581.patch
>
>
> Creating a combo JIRA for small performance optimizations.
> 1. changing from asynchronous action start to a synchronous one, to overcome
> the undue delay in transitioning from ::start:: control node to the actual
> first node, owing to a loaded queue. This delay has been observed to be close
> to 30 min at times in stress conditions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
