add recurring feature that allows running a job every N seconds#78
Merged
Conversation
* a recurring job has a schedule in zset with the next timestamp as the score * the frequency of the job is stored in a hash * on pop the frequency and the score are summed up to form the new score and added back to the zset * a delete recurring removes it from the zset and hash * add delete and pop operations run on a redis transaction
Contributor
Author
|
@gresrun I've fixed the failing test case |
gresrun
added a commit
that referenced
this pull request
Jun 8, 2015
add recurring feature that allows running a job every N seconds
Contributor
Author
|
thanks! 👍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
score
and added back to the zset
related issue #77