You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Chun-Hung Hsiao (JIRA)" <ji...@apache.org> on 2018/06/20 03:10:00 UTC
[jira] [Created] (MESOS-9010) `UPDATE_STATE` can race with
`UPDATE_OPERATION_STATUS` for a resource provider.
Chun-Hung Hsiao created MESOS-9010:
--------------------------------------
Summary: `UPDATE_STATE` can race with `UPDATE_OPERATION_STATUS` for a resource provider.
Key: MESOS-9010
URL: https://issues.apache.org/jira/browse/MESOS-9010
Project: Mesos
Issue Type: Bug
Components: storage
Reporter: Chun-Hung Hsiao
Assignee: Chun-Hung Hsiao
Since a resource provider and its operation status update manager run in different actors, for a completed operation, its `UPDATE_OPERATION_STATUS` call may race with an `UPDATE_STATE`. When the `UPDATE_STATE` arrives to the agent earlier, the total resources will be updated, but the terminal status of the completed operation will be ignored since it is known by both the agent and the resource provider. As a result, when the `UPDATE_OPERATION_STATUS` arrives later, the agent will try to apply the operation, but this is incorrect since the total resources has already been updated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)