-
Notifications
You must be signed in to change notification settings - Fork 80
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
Is the offering logging misleading? #44
Comments
Have you seen #26? Maybe that's related? |
Ahh this explains:
Maybe we should add some log output, to make this a bit more clear. For people experiencing the same, the 'problem' is that the mesos container running the tasktracker is probably given some value by property, 'mapred.mesos.tasktracker.cpus', in my case 0.15. So in my case 7 CPUs (per node) are completely taken by slots, plus 0.15 for the TT. Then Mesos tries to handout the remaining 0.85 CPU resources, but
|
I have a similar issue
I don't have maximum map / reduce tasks as 0. What else could be an issue? |
Hi,
I can't get my cluster of 80 CPUs and 200GB+ of mem to allocate the last 8.5 CPUs.
In the logging I can see this repeatedly:
I'm not sure why the hadoop/mesos is declining, every resource demand has been met.
The text was updated successfully, but these errors were encountered: