You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pushing a large application sometimes results in "Insufficient Resources" even though the "availabable memory" metric shows cellls which should be able to easily accommodate the application.
#955
Open
pusherofbrooms opened this issue
Aug 13, 2024
· 0 comments
On occasion, when we push a large (6GB) application, we might receive an "Insufficient Resources" error, even though there are cells with plenty of memory to accommodate the application (a couple of cells had as much as 22GB free) according to the AvailableResources metric presented in cfdot celll-states. Here are some relevant notes about our environment:
We use 128GB cells.
Unlike our other CF deployments, this one sees heavy "task" usage by one of our clients.
We are currently running v40.17.0 of cf-deployment
Adding a handful of cells allowed us to push applications normally.
Desired behavior
AvailableResources should accurately tell us if a large application can be pushed. Alternatively, if there is another metric we should be using to measure available resources, we'd like to know about it.
Affected Version
v40.17.0 of cf-deployment using diego v 2.100.0
The text was updated successfully, but these errors were encountered:
Current behavior
On occasion, when we push a large (6GB) application, we might receive an "Insufficient Resources" error, even though there are cells with plenty of memory to accommodate the application (a couple of cells had as much as 22GB free) according to the AvailableResources metric presented in
cfdot celll-states
. Here are some relevant notes about our environment:Desired behavior
AvailableResources should accurately tell us if a large application can be pushed. Alternatively, if there is another metric we should be using to measure available resources, we'd like to know about it.
Affected Version
v40.17.0 of cf-deployment using diego v 2.100.0
The text was updated successfully, but these errors were encountered: