Fix for MESOS-1688

[MartinWeindel]

As already explained in MESOS-1688, there are schedulers allocating memory only for the executor and not for tasks. For tasks only CPU resources are allocated in this case.
Such a scheduler does not get offered any idle CPUs if the slave has nearly used up all memory.
This can easily lead to a dead lock (in the application, not in Mesos).

Simple example:

1. Scheduler allocates all memory of a slave for an executor
2. Scheduler launches a task for this executor (allocating 1 CPU)
3. Task finishes: 1 CPU , 0 MB memory allocatable.
4. No offers are made, as no memory is left. Scheduler will wait of offers forever. Dead lock in the application.

To fix this problem, offers must be made if either CPU or memory is allocatable.

[tnachen]

hi @MartinWeindel, can you post on reviewboard instead? That's how all the mesos patches are reviewed.

[MartinWeindel]

post on reviewboard will follow