Bug #20667
Updated by Peter Amstutz almost 2 years ago
If the initial value of maxInstances is large, and the dispatcher becomes cloud quota limited (as opposed to getting 503 errors from controller) it does not adjust maxConcurrency and as a result does not recompute maxSupervisors based on the actual number of instances that can be run. maxSupervisors. This can result in inefficient usage or starvation because maxSupervisors does not reflect the actual limitations limit of the cluster.