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

Have qsetstate not need the current state given #7

Closed
wglass opened this issue Oct 4, 2013 · 0 comments
Closed

Have qsetstate not need the current state given #7

wglass opened this issue Oct 4, 2013 · 0 comments

Comments

@wglass
Copy link
Owner

wglass commented Oct 4, 2013

This will involve a hash in redis where the key is the job
unique key and the value the current state of the job.

Should return 1 when it works, 0 when the job is not around.

Must make sure the vaccum process removes the entry in this hash.

wglass pushed a commit that referenced this issue Nov 20, 2013
Before, there was a generic qsetstate script for setting arbitrary
states.  Now, there are just a handful of lua scripts that are well
aware of which states it will involve.

The states are represented as simple sets, with the exception of the
initial "scheduled" state, which is still a sorted set where "score" is
the epoch seconds scheduled time of the job.
@wglass wglass closed this as completed Nov 20, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant