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

4.0.1 => job no longer unique #117

Closed
phuongnd08 opened this issue Oct 7, 2015 · 4 comments
Closed

4.0.1 => job no longer unique #117

phuongnd08 opened this issue Oct 7, 2015 · 4 comments

Comments

@phuongnd08
Copy link
Contributor

After upgrade to 4.0.1 I start seeing jobs kept being queued without uniqueness awareness.
@mhenrixon
Copy link
Owner

You will have to specify the unique_lock for the job in that case. unique_lock: :until_executed for instance. The default lock type is now while_executing.

@mhenrixon
Copy link
Owner

@phuongnd08 check if the changes in 4277109 helps you understand the problem better. If not I will try to improve it some more.

@phuongnd08
Copy link
Contributor Author

I see hundred of job with the same type and arguments (no arguments actually) to be backlogged, so I don't think unique_lock value is the case.

@phuongnd08
Copy link
Contributor Author

Oh, after reading the text I understand what you are saying. Let me verify my case.

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
2 participants
@mhenrixon @phuongnd08