Framework might not receive status update when a just launched task is killed immediately

Our Marathon team are seeing issues in their integration test suite when Marathon gets stuck in an infinite loop trying to kill a just launched task. In their test a task launched which is immediately followed by killing the task – the framework does e.g., not wait for any task status update.

In this case the launch and kill messages arrive at the agent in the correct order, but both the launch and kill paths in the agent do not reach the point where a status update is sent to the framework. Since the framework has seen no status update on the task it re-triggers a kill, causing an infinite loop.