Affects Version/s: None
Before Mesos 1.4.0, on reboot agents would come up with different IDs. This meant that unreachable tasks on the node would never become terminal, forever blocking the recovery of resident tasks. In
MARATHON-2311 we created a mechanism to treat an offer with reservations for a task as an indication of the task being gone.
That is fixed in Mesos 1.4.0 and I have confirmed that terminal statuses are now received for unreachable tasks when rebooted hosts come back online.
Given resident task A running on agent X
If I stop the agent X
Then the task should be reported as UNREACHABLE
If I fail over the master, and then reboot agent X
Then I should get a terminal task status update for task A when agent X comes back online
Given a Mesos master running 1.3.x
When I start Marathon
Then Marathon should crash after connecting to Mesos and discovering that it is not 1.4.0 or later