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

Map/Reduce slot allocation is not ideal for small clusters #46

Open
tarnfeld opened this issue Mar 29, 2015 · 1 comment
Open

Map/Reduce slot allocation is not ideal for small clusters #46

tarnfeld opened this issue Mar 29, 2015 · 1 comment

Comments

@tarnfeld
Copy link
Member

In some situations, when using this framework in a very small mesos cluster (enough for only a few tasks) only map slots will be allocated and zero reduce slots. This can cause a dead-lock and although the effect should be reduced by the introduction of #33 (once the map slots became idle, reduce slots would take oveR) in some cases with certain resource allocations it can still occur.

I guess we should do a better job at allocating a decent map/reduce slot ratio.

@tarnfeld
Copy link
Member Author

The ticket #47 is also a little relevant here.

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