tree 1b015272f2813e9e915eb637328ed9d892f47af2
parent 6be17200b8084ad3524e7d450c411765b3214c0f
author Benjamin Mahler <bmahler@apache.org> 1598918194 -0400
committer Benjamin Mahler <bmahler@apache.org> 1599759140 -0400

Added a regression test for MESOS-9609.

Per MESOS-9609, it's possible for the master to encounter a CHECK
failure during agent removal in the following situation:

  1. Given a framework with checkpoint == false, with only
     executor(s) (no tasks) running on an agent:
  2. When this agent disconects from the master,
     Master::removeFramework(Slave*, Framework*) removes the
     tasks and executors. However, when there are no tasks, this
     function will accidentally insert an entry into
     Master::Slave::tasks! (Due to the [] operator usage)
  3. Now if the framework is removed, we have an entry in
     Slave::tasks, for which there is no corresponding framework.
  4. When the agent is removed, we have a CHECK failure given
     we can't find the framework.

This test runs through the above scenario, which no longer crashes
given the fix applied.

Review: https://reviews.apache.org/r/72830