bdoyle0182 commented on issue #5368: URL: https://github.com/apache/openwhisk/issues/5368#issuecomment-1370185863
I’ve played with action concurrency > 1 on the new scheduler and it works as is however I don’t think there’s been any verification to production readiness. The scheduler doesn’t make any decisions right now on container creations regarding an action with concurrency so I wouldn’t be shocked if there’s some bug with setting and inserting the action throttled flag in etcd when action concurrency is in use. On Fri, Dec 30, 2022 at 5:46 AM Dino Keylas ***@***.***> wrote: > Thanks for your response! @style95 <https://github.com/style95> > Also sorry for my late reply. Just try to find out the problem, but it > takes time for my since I'm beginner in Scala. > > I have seen the logs and didn't found any error log related to this issue. > According my experiment, the throttling is enable for action. I'm able to > invoke other actions under same namespace with perfTest. > > The error that I described above only happen when action concurrency = 100 > (I increased the action concurrency from 1 to 100). > If the action concurrency = 1, the error not occur. > > Is new Scheduler well supported for action concurrency? > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/openwhisk/issues/5368#issuecomment-1367852029>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AC2UI6ZAY4L2DFJIIWSXFEDWP24QHANCNFSM6AAAAAATK6X2ZU> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org