You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:57:09 UTC
[jira] [Commented] (OOZIE-258) GH-361: Throttle coordinator
action/workflow creation per coordinator job
[ https://issues.apache.org/jira/browse/OOZIE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099922#comment-13099922 ]
Hadoop QA commented on OOZIE-258:
---------------------------------
mislam77 remarked:
Please comment on these open questions:
* How the throttling value/order should be defined?
- system wide/ System defined.
- per job based/ User defined.
> 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