Details
Critical Description
Since the mesos driver synchronizes all callbacks, it's very important to return as quickly as possible to avoid blocking other callbacks. In the case of resourceOffers, we start by calling storage.write, which will stall if the write lock is held. In very large, busy clusters, we've observed resourceOffers routinely taking > 1 second, which can lead to delays in receiving status updates.
I suggest the entire body of resourceOffers be asynchronous to prevent it from backing up status updates.