[
https://issues.apache.org/jira/browse/OOZIE-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815219#comment-13815219
]
Virag Kothari commented on OOZIE-1581:
--------------------------------------
Couple of things discussed with Mona:
OOZIE-243 adds the control nodes to db and all the control nodes follow the
command life cycle. Instead of optimizing the execution of commands for this
nodes (async to sync), can we devise a way such that the control nodes can be
configured to be not added as wf_actions in database? In this case, they wont
go through the command life cycle like action nodes.
While synchronously calling command, it would be good to check if we can pass
the bean object to another command directly, so the other command doesn't need
to perform db operations like loadState() and verifyPreCondition(). E.g
CoordActionReady to CoordActionStart in the patch. Also, please check whether
this type of optimization can be done at other places.
> 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: trunk
>
> Attachments: OOZIE-1581-2.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.1#6144)
