Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Executor failing when request burst is more than poolsize #1883

Closed
swaroopnuli opened this issue Dec 14, 2020 · 0 comments · Fixed by #1890
Closed

Executor failing when request burst is more than poolsize #1883

swaroopnuli opened this issue Dec 14, 2020 · 0 comments · Fixed by #1890

Comments

@swaroopnuli
Copy link

Fission/Kubernetes version
AWS EKS 1.17.1

$ fission --version
$ kubectl version
client:
  fission/core:
    BuildDate: "2020-10-20T14:43:45Z"
    GitCommit: 52508e19343ef93da4ce8960908c5569f44da225
    Version: 1.11.2
server:
  fission/core:
    BuildDate: unknown
    GitCommit: unknown
    Version: unknown

Kubernetes platform (e.g. Google Kubernetes Engine)
AWS EKS
Describe the bug

When the HTTP function call request burst is more than the poolsize, the new pods are not spawned.
To Reproduce

function poolsize: 20
concurrent request burst: 100 (substantially higher than poolszie)
function HTTP trigger: POST
Expected result

unmanaged pods should scale out and handle more load
Actual result
executed failing and no more scaling up of the pods

Screenshots/Dump file

fission-dump_1607955728.zip

$ fission support dump

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants