travigd opened a new issue #4974: URL: https://github.com/apache/openwhisk/issues/4974
<!-- We use the issue tracker for bugs and feature requests. For general questions and discussion please use http://slack.openwhisk.org/ or https://openwhisk.apache.org/contact.html instead. Do NOT share passwords, credentials or other confidential information. Before creating a new issue, please check if there is one already open that fits the defect you are reporting. If you open an issue and realize later it is a duplicate of a pre-existing open issue, please close yours and add a comment to the other. Issues can be created for either defects or enhancement requests. If you are a committer than please add the labels "bug" or "feature". If you are not a committer please make clear in the comments which one it is, so that committers can add these labels later. If you are reporting a defect, please edit the issue description to include the information shown below. If you are reporting an enhancement request, please include information on what you are trying to achieve and why that enhancement would help you. For more information about reporting issues, see https://github.com/apache/openwhisk/blob/master/CONTRIBUTING.md#raising-issues Use the commands below to provide key information from your environment: You do not have to include this information if this is a feature request. --> ## Environment details: Deploying to Kubernetes on GKE with node pool autoscaling ## Steps to reproduce the issue: 1. Launch many concurrent actions (more than can be handled by the current node pool) 2. Observe that new pods are scheduled and in pending state while autoscaling is occurring 3. Notice that even if some of the activations finish within (eg) 10s, the other actions are still waiting on the pod to be spun up ## Provide the expected results and outputs: OpenWhisk should perform the autoscaling, but only distribute activations amongst the READY pods (eg after calling the `/init` endpoint on the container). ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
