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

FIFO strategy #415

Closed
nononoy opened this issue Aug 6, 2019 · 3 comments
Closed

FIFO strategy #415

nononoy opened this issue Aug 6, 2019 · 3 comments

Comments

@nononoy
Copy link

nononoy commented Aug 6, 2019 •
edited
Loading

Hi. I tried all the strateges, but didn't figure it out. What if I need to handle all jobs in strict order one after another. Job 1 -> Job 2 -> Job 3. Can I do such FIFO without custom locks?
@mhenrixon
Copy link
Owner

That is how it works by default. You are looking for :until_executed

@mhenrixon
Copy link
Owner

Oh no wait, the subsequent jobs will just be dropped. You probably have to look at someother gem for that. Think Sidekiq batches can achieve that

@nononoy
Copy link
Author

nononoy commented Aug 7, 2019

Unfortunatelly it not works with reschedule. "Stack level too deep" error if I bump second task when the first one is under processing.

@nononoy nononoy closed this as completed Aug 7, 2019
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 @nononoy