-
Notifications
You must be signed in to change notification settings - Fork 775
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
Scale fission function pods per function call #2944
Comments
@LyKos4 Have you tried increasing the concurrency?
|
Yes, I have tried changing concurrency, yolo and rpp. |
In that case
Did you see a different behaviour with |
With yolo true there were more that one pods created for a function run. |
This should not happen. Only one pod per function call is created with |
I am talking for the fission function pods and I am checking which run a specific function with the command fission function pods --fnNamespace=(namespace) --name=(function-name) |
Please try below steps and post the results if you see different results. I am using
Check for env pods
Verify that no function pods exist at the moment.
|
What I need?
I need to scale up fission function pods when same function is called multiple times.
What happens now?
If a do eg. 3 requests of the same fission function, on pod will be up to run all those 3 which causes a delay.
I can see that by running fission function pods --fnNamespace=(namespace) --name=(function_name)
What I have tried?
I tried to set --concurrency 1 or --yolo true. Both indeed create new pods each time a fission function is called but then for the same piece of code new pods are created. So multiple pods are created for same call of a fission function which at the end doesn't seem to get the expected results.
Is there a way to create only on new fission-function pod each time a fission functionis supposed to run?
The text was updated successfully, but these errors were encountered: