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

Allow a slave to "fail" a piece of work #7

Open
mvr opened this issue Jul 31, 2015 · 5 comments
Open

Allow a slave to "fail" a piece of work #7

mvr opened this issue Jul 31, 2015 · 5 comments

Comments

@mvr
Copy link
Contributor

mvr commented Jul 31, 2015

In Kesha, some of the zones might be way harder than others. If a zone takes too long, we want to "fail", and send that piece of work to the end of the queue to be tried again later. This way we can get most of the zones done early.

@jamiecook
Copy link
Contributor

jamiecook commented Jul 31, 2015 via email

@mvr
Copy link
Contributor Author

mvr commented Jul 31, 2015

The idea is we would kill a particular bit of work after some preset timeout, then put it at the end of the queue to be done for real after everything else.

@jamiecook
Copy link
Contributor

To what end? Are we streaming the results back so that partial results are useful?

@mvr
Copy link
Contributor Author

mvr commented Jul 31, 2015

Yeah, results get streamed back. The ruby code around Kesha does some post-processing that can happen as soon as each bit of work is done by a slave. Also, if for some reason one of the slaves hangs, we don't want it to be useless for there rest of a run.

@jamiecook
Copy link
Contributor

jamiecook commented Jul 31, 2015 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants