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

Store current job state directly in Riak #122

Open
dmitrizagidulin opened this issue Dec 17, 2015 · 0 comments
Open

Store current job state directly in Riak #122

dmitrizagidulin opened this issue Dec 17, 2015 · 0 comments
Milestone
v0.2.0 - (General...

Comments

@dmitrizagidulin
Copy link
Contributor

For the same reasons as #121, we should store the state of Explorer long-running jobs in Riak, instead of in memory as is currently done.
This becomes important in a multi-Explorer-node setup (such as for Riak Mesos), so that more than one Explorer node doesn't accidentally start the same job when it could just wait for another node to finish.
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
v0.2.0 - (General Release - Prod Mode)
Development

No branches or pull requests
1 participant
@dmitrizagidulin