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

Internal Error 500 #21

Open
husky-parul opened this issue Mar 25, 2018 · 1 comment
Open

Internal Error 500 #21

husky-parul opened this issue Mar 25, 2018 · 1 comment

Comments

@husky-parul
Copy link

husky-parul commented Mar 25, 2018

Hi

I am trying to use OpenWhisk over OpenShift. The goal is to run embarrassingly parallelise algorithmic tasks and spinning large number of workers to test the scalability of the system. My concern is not the problem I am solving. It is to find out how many workers can be spinned.

I set these properties

name: WHISK_ACTIONS_INVOKES_CONCURRENT
  description: Default number of concurrenct actions per user
  value: "1000000"
  required: true
- name: WHISK_ACTIONS_INVOKES_CONCURRENT_IN_SYSTEM
  description: Number of concurrent actions allowed across the entire system
  value: "1000000"
  required: true
- name: WHISK_ACTIONS_INVOKES_PER_MINUTE
  description: Default number of action invocations per minute per user
  value: "1000000"
   required: true

For values greater than 10000, I get 500 Internal error. Is there a limit to these values. If yes, is there a way to override them?

@husky-parul husky-parul changed the title Interval Error 500 Internal Error 500 Mar 25, 2018
@bbrowning
Copy link
Member

I don't think there's any built-in limit to those values, although I could be wrong. When you say you get a 500 error, what component gave that error? Where did you see the error? You should be able to check the logs of the controller and/or invoker pods to see what's going on.

With that said, adjusting these values won't magically make the system scale to extremely high levels. You have to actually deploy a large enough cluster to handle the amount of load you want to throw at it. If you wanted to be able to run 1 million concurrent actions in the cluster as you show here you'll need a gigantic cluster with terabytes of RAM and hundreds if not thousands of Invoker nodes.

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

No branches or pull requests

2 participants