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

Find a better solution for died Huey worker... #11

Open
jedie opened this issue Dec 17, 2020 · 2 comments
Open

Find a better solution for died Huey worker... #11

jedie opened this issue Dec 17, 2020 · 2 comments

Comments

@jedie
Copy link
Collaborator

jedie commented Dec 17, 2020

In #10 we add a work-a-round for died Huey worker.

But this is no a good solution, because non affected, running tasks will also get a "unknown" signal :(

@jedie
Copy link
Collaborator Author

jedie commented Feb 7, 2022

non affected, running tasks will also get a "unknown" signal :(

Maybe we should check/reset existing unknown signal entries for all new signal for the same task_id ?

@expresspotato
Copy link

Hello,

This bug seems to affect us in two distinct ways:

  1. We get race conditions on startup, where initial tasks are started and huey monitor initialization appears to execute afterwards, setting cleanly started and executing tasks to unknown

  2. At scale, I suspect this will just clear already running tasks if another consumer process (on another server) is brought online...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants