Yesterday my team mate came to me with a requirement of changing default throttle value (12) in Oozie so that he can test few scenarios. As per documentation we can see in oozie-default.xml property oozie.service.coord.default.throttle
Default throttle for a coordinator job to determine
how many maximum action should be in WAITING state at
the same time. In Cloudera Manager we can’t change this value directly because there is no option to change it. Before implementing this change let’s understand little more about it.
A coordinator job periodically creates coordinator actions. Therefore, if we can regulate this materialization, the ultimate number of outstanding actions can be controlled. Oozie provides a user-level control knob called throttle, which a user can specify in her coordinator XML. This controls how many maximum coordinator actions can be in the WAITING state for a coordinator job at any instant. If no value is specified, the system default value of 12 is used. While a user can specify any value for this, there is also a system-level upper limit that an administrator can tune. This system-level limit is calculated by multiplying the throttling factor (property oozie.service.coord.materialization.throttling.factor and the maximum internal processing queue size (property oozie.service.CallableQueueService.queue.size) defined in oozie-site.xml. In short, this setting can be tuned both at the system and the user level through the oozie-site.xml and coordinator XML, respectively.
Example: If we want default job "5" then change
oozie.service.coord.materialization.throttling.factor = .05
As default value of
oozie.service.CallableQueueService.queue.size = 100
So 100 x.05 = 5"
I was looking for this. Thanks