[
https://issues.apache.org/jira/browse/OOZIE-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727852#comment-14727852
]
Purshotam Shah commented on OOZIE-2345:
---------------------------------------
bq. oozie.workflow.parallel.fork.action.start - Can we make this true by
default in oozie-default.xml ?
I think we should keep it to false by default and if anyone has any issue he
can turn it on.
One caveat of approach that if one has small queue size and and there are lot
of actions in fork job.
Than signalxcommand will get stuck till all command completes (This include
wait for queue to free up)
> Parallel job submission for forked actions
> ------------------------------------------
>
> Key: OOZIE-2345
> URL: https://issues.apache.org/jira/browse/OOZIE-2345
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
> Assignee: Purshotam Shah
> Attachments: OOZIE-2345-V3.patch
>
>
> We have few customers whose SLA is 8 min. They have around 30 actions. There
> are 25 actions in fork.
> Though forked action jobs runs parallely in the cluster, forked action job
> submission is sequential.
> Whenever NN is slow, job submission takes more time. Even if job submission
> is delay for 30 sec. Total WF delay will be ~12 min.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
