Using a Scaled-Out Executor Component Instance
A scaled-out Executor component instance is one that has multiple execution nodes, or gears, on which executions are scheduled.
If the component is scaled out, the Concurrency Level configuration setting controls how many concurrent executions are permitted on each node. For example, if an Executor component is scaled out across 4 nodes with a concurrency level of 28, it can have up to 112 executions in progress at the same time.
Because executions are assigned to nodes on a round-robin basis, it is possible for a node that has reached execution capacity to reject an execution request. When this happens, the client receives a 429 status code response. After receiving this response, the client should retry the request until the execution is accepted and completed. As the total maximum execution capacity is approached, the client might see many 429 responses to a request before an available node can be located. This is expected, and it is recommended to balance the scaled-out node capacity to be above the expected peak.
Only the Staging and Production lifecycle stages of the component can be scaled out. It is not possible to scale out an instance in the Design stage.
© 2001-2025 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.