Open bisgaard-itis opened 2 months ago
@sanderegg I can see you have been working on this, it would be great to discuss what a potential solution could be. My immediate intuition is that other tasks in the event loop which are also requiring the lock should await until the lock is released instead of throwing an exception straight away. I guess that's how a mutex would work when threading.
@sanderegg I can see you have been working on this, it would be great to discuss what a potential solution could be. My immediate intuition is that other tasks in the event loop which are also requiring the lock should await until the lock is released instead of throwing an exception straight away. I guess that's how a mutex would work when threading.
One approach would be to remove the blocking=False
here and instead introduce a blocking timeout.
Closing this due to this
Reopening this due a comment by @sanderegg. Potential solutions:
create_study_job
endpoint takes the inputs as body. So one would have to pass a list of input params or alternatively factor out the setting og the inputs to another endpoint. The workaround is to use templates and take advantage of a bug that you have right now there :-)
Is there an existing issue for this?
Which deploy/s?
No response
Current Behavior
After resolving performance issues in
storage
I now see a lot of 502 status codes from Webserver when running https://github.com/wvangeit/osparc-pyapi-tests/tree/master/noninter1 againstdalco-master
. After digging into graylog I see that many (perhaps even all) arise from the same exception type in thewb-api-server
:This exception makes sense because the project attempts to create 100 clones of the project '6dc3f228-06cb-11ef-bb37-02420a00f1d5' at the same time. If that operation requires a lock then some of these will definitely fail. The question is how to solve it.
Expected Behavior
No response
Steps To Reproduce
No response
Anything else?
No response