markusthoemmes commented on issue #2245: new ContainerPool aggressively restarts containers under load URL: https://github.com/apache/incubator-openwhisk/issues/2245#issuecomment-301683810 I would only force queue the messages if the container is **really** maxed out. That means: No containers available and each namespace has exactly 1 container (that's an overload scenario basically). As commented in the PR, I would always schedule a container of the most consuming resource for removal, even if it's in `Busy` state. That action would still finish, but the other action can go on and no starvation happens. This scheme induces a bit of overcommit, which I tend to think we can live with. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
With regards, Apache Git Services
