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

Broker should only ask for jobs it can execute #46

Open
turicas opened this issue Mar 1, 2013 · 1 comment
Open

Broker should only ask for jobs it can execute #46

turicas opened this issue Mar 1, 2013 · 1 comment

Comments

@turicas
Copy link
Contributor

turicas commented Mar 1, 2013

Currently, Router announces that there is a new job, but it does not say which worker Broker should execute for this job until Broker asks for the job. If Broker doesn't have the worker for it, the job will fail. So, I propose:

  • Router, when announcing jobs, should specify worker name (and maybe job id)
  • Broker should only ask for jobs if it has the worker specified (or it can specify directly in the get job message which worker it wants)

Optionally, Broker can send all workers it has loaded to Router when it starts, so Router will know all workers it can execute in the entire cluster.

@turicas
Copy link
Contributor Author

turicas commented Mar 1, 2013

This issue is a bit related to #29.

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