Setting a Maximum Number of Starting Containers
Page last updated:
This topic describes how to use the auctioneer job to configure the maximum number of app instances starting at a given time. This prevents Diego from scheduling too much new work for your platform to handle concurrently. A lower default can prevent server overload during cold start, which may be important if your infrastructure is not sized for a large number of concurrent cold starts.
The auctioneer only schedules a fixed number of app instances to start concurrently. This limit applies to both single and multiple Diego Cells. For example, if you set the limit to five starting instances, it does not matter if you have one Diego Cell with ten instances or five Diego Cells with two instances each. The auctioneer will not allow more than five instances to start at the same time.
If you are using a cloud-based IaaS, rather than a smaller on-premise solution, Cloud Foundry recommends leaving the default at
You can configure the maximum number of started instances by changing the
diego.auctioneer.starting_container_count_maximum property in the Diego manifest.
- Open the Diego manifest in a text editor.
- Find the
- Set the maximum number of instances the auctioneer should allow to start.
- Save the changes and redeploy BOSH.
For example, the following Diego manifest excerpt shows the
diego.auctioneer.starting_container_count_maximum property set to
Create a pull request or raise an issue on the source for this page in GitHub
diego.auctioneer.starting_container_count_maximum: description: "Maximum number of inflight container starts allowed globally. Value of 0 or less indicates no limit." default: 100