Random 503 errors from Weblate

[jmdem]

Describe the issue
Hi, first thanks for creating this amazing app !
We recently faced a strange issue with our hosted docker version of Weblate. We use Weblate to manage and serve translations, and we noticed that on a ratio of 1/10, some request were returning a 503. The Weblate API is often requested, when our users logs in one of our web apps. As said, most of the time, everything just works. But randomly, the server seems to be unable to serve the data, no matter which route.
Is there anything we're missing here ? Reading the docs, we didn't see anything that can cause this random issue.

Any help is much appreciated, thank you.

I already tried
We already tried to stress the Weblate service API, with many concurrent requests, and up to 100 concurrent request, it responds well.
Describe the steps you tried to solve the problem yourself.

• I've read and searched the docs and did not find the answer there.
  If you didn’t try already, try to search there what you wrote above.

To Reproduce the issue

Steps to reproduce the behavior:

1. Go to '...'
2. Scroll down to '...'
3. Click on '...'
4. See error

Expected behavior

Screenshots

Exception traceback

Server configuration and status

Weblate installation: weblate.org service / Docker / PyPI / other

Weblate deploy checks

Additional context

[nijel]

It can be that all uwsgi workers are busy, you can try increasing that: https://docs.weblate.org/en/latest/admin/install/docker.html#envvar-UWSGI_WORKERS

[github-actions]

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you!

[github-actions]

This issue has been automatically marked as stale because it has not had any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!

[jmdem]

Thanks for the reply, we keep monitoring the issue, if we need to we'll try this solution and see if it improves in someway.
B.R.

[github-actions]

This issue has been automatically marked as stale because it has not had any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!