On Marathon 1.4.2 we encountered a problem where when the Mesos Agent ID changes on a node, marathon is not able to re-discover the reserved resources on that node.
Here's the /v2/info for marathon
A few select items from the mesos agent logs:
The tasks actually EXIST in mesos, but marathon doesn't seem to know about them. When I look at the link for the marathon app instances, it has the correct app ids, but the slave ID in the link is the old one, not the new one.