mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anindya Sinha (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MESOS-7308) Race condition in `updateAllocation()` on DESTORY of a shared volume.
Date Fri, 24 Mar 2017 21:42:41 GMT
Anindya Sinha created MESOS-7308:
------------------------------------

             Summary: Race condition in `updateAllocation()` on DESTORY of a shared volume.
                 Key: MESOS-7308
                 URL: https://issues.apache.org/jira/browse/MESOS-7308
             Project: Mesos
          Issue Type: Bug
          Components: general
            Reporter: Anindya Sinha
            Assignee: Anindya Sinha


When a {{DESTROY}} (for shared volume) is processed in the master actor, we rescind pending
offers to which the volume to be destroyed is already offered to. Before allocator executes
the {{updateAllocation()}} API, offers with the same shared volume can be sent to frameworks
since the destroyed shared volume is not removed from {{slaves.total}} till {{updateAllocation()}}
completes. As a result, the following check can fail:
{code}
  CHECK_EQ(
      frameworkAllocation.flatten().createStrippedScalarQuantity(),
      updatedFrameworkAllocation.flatten().createStrippedScalarQuantity());
{code}

We need to address this condition by not failing the {{CHECK_EQ}}, and also ensuring that
the master's state is restored to honor the {{DESTROY}} of the shared volume.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message