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

JobQueue sets job.name as host #1307

Open

dioh opened this issue Apr 13, 2015 · 1 comment

dioh commented Apr 13, 2015

Using this behaviour fixes the task to a node prior knowing if it's available on assignment.

Use case:

assign Task 1 -> N1
Task 2 -> N2
Task 3 -> N1

N2 ends computation before N1 so Task 3 is assigned to run in N1.
N1 is now currently running T1 and T3 and N2 is idle.

Am I loosing something here?

If code example is needed I can provide but I need some time.

Member

bitprophet commented May 4, 2015

Can you expand/clarify this? Maybe give a specific example from your environment (sanitized, of course :)) if you're able.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment