[
https://issues.apache.org/jira/browse/OOZIE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101935#comment-13101935
]
Hadoop QA commented on OOZIE-258:
---------------------------------
mislam77 remarked:
No. it was not implemented.
There is similar thing in WF submission when a lot coordinator actions ready to
execute, oozie throttles using "concurrency" and order such as FIFO/LIFO.
I think you were confused with this.
The issue is for throttling during action creation.
Throttling configuration in system level might create some future issue. For
example, at some point, a user has 100 actions to be materialized but system
throttling value is :7. All 7 actions are waiting for data . However, he has
the data for 10th and 12th instances. In this case, if he could give the
throttling value of 12, his ready jobs would have been started.
> GH-361: Throttle coordinator action/workflow creation per coordinator job
> -------------------------------------------------------------------------
>
> Key: OOZIE-258
> URL: https://issues.apache.org/jira/browse/OOZIE-258
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> Currently, if there are thousands of eligible coordinator actions to be
> created (e.g. catch-up mode) for one coordinator job, oozie creates all of
> them once and overloading the system.
> This thing needs to be controlled and should only materialized X number of
> active actions per coordinator job. The
> value of X should be configurable whether in oozie level or per job level
> that needs to be decided.
> In addition, there should be a way for customer to define the order by which
> job creation should be followed. For
> example, if there are 1000 actions ready to be created which X actions should
> be created first. Such as FIFO or LIFO.
> This will definitely reduce the load on the internal queue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
