Re: ERR Failed to stage application: insufficient resources
|
Matthew Sykes <matthew.sykes@...>
There are three resources that you can run out of that would result in that
toggle quoted messageShow quoted text
error: memory, disk, or containers. [1] These resources are validated during the auction that determines where a task or LRP will land. Advertised memory and disk resources are configurable [2] in diego and container limits are defined in garden [3]. If you don't specify memory or disk for diego, the actual system capacity is advertised for placement without any overcommit. That means if you're running 8 containers with a 2048M limit on a 16GB cell, you're out of memory capacity - regardless of how much memory is actually used. Many deployments can get away with 2 to 3x overcommit on memory and disk but it really depends on the kinds of apps that are being deployed. [1]: https://github.com/cloudfoundry-incubator/rep/blob/320f5e9ff0ba2a7bb1294927cbe31ce5af40c987/resources.go#L63-L68 [2]: https://github.com/cloudfoundry-incubator/diego-release/blob/develop/jobs/rep/spec#L55-L60 [3]: https://github.com/cloudfoundry-incubator/garden-linux-release/blob/develop/jobs/garden/spec#L65-L67
On Thu, Jan 28, 2016 at 11:52 AM, Stanley Shen <meteorping(a)gmail.com> wrote:
when I push an application to CF with diego deployed, the app failed for --
Matthew Sykes matthew.sykes(a)gmail.com
|
|
|