dinok97 opened a new issue, #5368:
URL: https://github.com/apache/openwhisk/issues/5368

   <!--
   We use the issue tracker for bugs and feature requests. For general 
questions and discussion please use https://openwhisk.apache.org/slack.html or 
https://openwhisk.apache.org/community.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.
   -->
   
   I did performance test for **Openwhisk with New Scheduler** (pull-based 
activation). When it comes to test with 5000 RPS, hundred of error happened. 
Then, I checked it by invoked the tested action from WSK CLI and get error 
response 
   
   `error: Unable to invoke action 'perfTest': Too many requests (code 
74bd570f6b048c437664907592f07bbe)`.
   
   I waited for 4 hours with hope that the action will be normal again. But it 
seems like the action cannot be normal anymore (always return 'too many 
requests' error).
   
   After long of waiting, I try to re-created the function (delete existing 
function and create the new one with the same name and kind) and still got `too 
many requests` error.
   
   Is that the true behavior? or that is a bug? 
   
   ## Environment details:
   
   * distributed deployment, all VMs  (AWS EC2 Instance) are Linux
   * 2 VMs Controller, 4 VMs Invoker, 2 VMs Scheduler, 1 VMs ETCD
   
   ## Steps to reproduce:
   1. Create simple nodejs action, for example `perfTest` action  
   2. Test  `perfTest` action with 5000 RPS for 1 minutes. We use `wrk 2` as a 
tool. Below is the commad 
       `wrk -t10 -c10 -d60s -R5000 --script post.lua --latency 
https://owserver/api/v1/namespaces/_/actions/perfTest?blocking=false`
   3. Wait until test finished with some of errors
   4. Try to invoke `perfTest` action
     
   
   ## Expected results:
   
   ```
   invocation success:
   
   {
       "params": {}
   }
   ```
   
   
   ## Actual results:
   
   ```
   invocation error:
   
   error: Unable to invoke action 'perfTest': Too many requests (code 
74bd570f6b048c437664907592f07bbe)
   Run 'wsk --help' for usage.
   ```
   
   ## Additional information:
   * The `perfTest`action back to normal after Scheduler was restarted. There 
us no other way besides that.
   


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@openwhisk.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to