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.

Sign up for GitHub

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

Jump to bottom

Worker consumes a job more then expected #148

Closed
adzimzf opened this issue Jan 23, 2020 · 2 comments
Closed

Worker consumes a job more then expected #148

adzimzf opened this issue Jan 23, 2020 · 2 comments

Comments

@adzimzf
Copy link

adzimzf commented Jan 23, 2020

We push a job to gocraft/work use EnqueuInUniqueByKey. we enqueue a unique job to running 5 minutes after it enqueued. Everything works like a charm until several days ago somehow the worker consumed multiple jobs with the same unique job at the same time. around 1K jobs are consumed for 30 minutes.

Anyone has experienced that case?
@caldempsey
Copy link
Contributor

caldempsey commented Feb 26, 2020 •
edited

@adzimzf Hey! Which release or commit do you use for your Gocraft library? Curious as the latest master branch seems to be bugged, and the EnqueueInUniqueByKey method doesn't seem to exist on the latest release.

@nghianguyen1tiki
Copy link

yeah, me too. enqueue onces, executed twice!

@austintaylor austintaylor mentioned this issue Aug 5, 2021
Open
@elliotcourant elliotcourant mentioned this issue Sep 1, 2023
Closed
@elliotcourant elliotcourant mentioned this issue Sep 27, 2023
Closed
@adzimzf adzimzf closed this as completed Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@caldempsey @adzimzf @nghianguyen1tiki