Skip to content
New issue

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

Respawning uwsgi processes causes multiple task invocations #21

Open
guglielmo opened this issue Jun 17, 2020 · 1 comment
Open

Respawning uwsgi processes causes multiple task invocations #21

guglielmo opened this issue Jun 17, 2020 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@guglielmo
Copy link
Member

Whenever a uwsgi process dies, in the middle of a spooled task execution, it is respawned.

Since this happens before the task is marked as processed, and removed from the spooler (or re-spooled with a later execution time), the respawned uwsgi process proceeds with reading the file in the spooler once again, untill the crash causes are resolved.

This can potentially cause hundreds of invocations per minutes, flooding the disk with log files.

A mechanism to control the re-spawning should be used.

@guglielmo guglielmo self-assigned this Jun 17, 2020
@guglielmo guglielmo added the bug Something isn't working label Jun 17, 2020
@guglielmo
Copy link
Member Author

There is maybe a configuration parameter in uwsgi.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant