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
