-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add ability to check async workers status #32
Comments
I'm still under impression, that celery should raise an error when workers lost, like this. Not sure, what was the exact situation on Sunday, didn't have a look into it yet. |
@a-milogradov We had similar issues previously, for example, ecwidservice local worker went silent due to incorrect parameter order in the configuration. |
I believe it died because of this:
but before that, connection was lost, maybe redis was restarted:
upd. reduced verbosity of comment |
yes, it did died because of that. But this ticket's aim is to improve detection, not prevent the cause. |
Sentry event is a part of detection system. I think it's important understanding why it died silently without sentry report. |
As of now, this lib has a major flow which negates its purpose.
If a service async worker dies we don't detect that and still continue to respond with 200 on status.
So we can't rely on those status endpoints in our monitoring which makes it hard to understand why we have issues like this:
https://github.com/yola/production/issues/9075
https://github.com/yola/production/issues/9076
The text was updated successfully, but these errors were encountered: