We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think that the workers are being overloaded with requests 🤔
[pid: 83|app: 0|req: 340/1028] 10.99.16.1 () {66 vars in 1353 bytes} [Thu Sep 19 17:08:59 2024] GET /api/v1/destruction-lists/?ordering=-created => generated 15106 bytes in 77 msecs (HTTP/1.0 200) 10 headers in 487 bytes (1 switches on core 0) [pid: 83|app: 0|req: 341/1029] 10.99.16.1 () {66 vars in 1353 bytes} [Thu Sep 19 17:08:59 2024] GET /api/v1/destruction-lists/?ordering=-created => generated 15106 bytes in 73 msecs (HTTP/1.0 200) 10 headers in 487 bytes (1 switches on core 3) worker 3 killed successfully (pid: 97) Respawned uWSGI worker 3 (new pid: 104)
The text was updated successfully, but these errors were encountered:
Maybe increasing the harakiri value may solve the problem as uwsgi may recycle workers that worked on long requests.
Sorry, something went wrong.
No branches or pull requests
I think that the workers are being overloaded with requests 🤔
The text was updated successfully, but these errors were encountered: