Mesos logic to offer resources to marathon framework related

[max]

I've slaves which are tied to tags and the same can be used as constraints while deploying applications via marathon on mesos. However after some deployments I noticed that mesos is no longer offering resources to marathon from the slave group with a specific tag. Now I know the slaves with this tag x has unused resources and and the same can be confirmed by looking at the number of mesos tasks running on them or by looking at logs where mesos confirms to recover a lot of resources from them. Not sure how the mesos logic works while offering resources to frameworks. What I could figure out from mesos documentation is that the filtering is done at framework level and in my scenario mesos should offer resources from all slaves irrespective of the tag they have and the framework should chose which slave they want to deploy on based on tag. Now I'm wondering if there is a way to figure out why mesos is not offering resources from the slaves with a specific tag anymore to marathon framework. Any info would help.