Hi Roy, The waiting jobs indeed takes some resources from oozie server. Oozie periodically (every minute) checks the input data dependency for waiting coordinator actions. At high load, this could create a substantial overhead on Oozie server. If your system is lightly loaded , you can easily change that value either 1. In system level, by overriding the property oozie.service.coord.default.throttle in ooze-site.xml 2. Per job level, in the control section of coordinator.xml
Hope this helps. Regards, Mohammad ________________________________ From: Roy Velich <[email protected]> To: [email protected] Sent: Tuesday, October 30, 2012 10:46 AM Subject: Throttle property Hello, I wonder what are the benefits, for the user, by setting the throttle property in the oozie coordinator XML file. considering that a workflow instance in a WAITING state does not take any system resources, what does limiting the number of workflow instances in a WAITING state gives in practice? Thanks! :-)
