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

Configuring the max map/reduce slots per task tracker to zero causes no offers to be accepted #26

Open
tarnfeld opened this issue Jul 6, 2014 · 0 comments
Open

Configuring the max map/reduce slots per task tracker to zero causes no offers to be accepted #26

tarnfeld opened this issue Jul 6, 2014 · 0 comments
Labels
bug scheduler

Comments

@tarnfeld
Copy link
Member

tarnfeld commented Jul 6, 2014

Kind of obvious, but something I misconfigured and took be a really long time to get to the bottom of. I just assumed if I configured it to zero no maximum would apply (which was the desired behaviour).

Perhaps it's something that should be documented, or an exception be thrown to highlight the configuration error. Alternatively make zero mean no maximum?

What's the reason you might want to limit the number of slots per TT?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug scheduler
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tarnfeld