You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Bannier (JIRA)" <ji...@apache.org> on 2017/12/04 13:10:00 UTC
[jira] [Assigned] (MESOS-8222) Add resource versions to
RunTaskMessage
[ https://issues.apache.org/jira/browse/MESOS-8222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bannier reassigned MESOS-8222:
---------------------------------------
Assignee: Benjamin Bannier
Sprint: Mesosphere Sprint 69
Story Points: 3
> Add resource versions to RunTaskMessage
> ---------------------------------------
>
> Key: MESOS-8222
> URL: https://issues.apache.org/jira/browse/MESOS-8222
> Project: Mesos
> Issue Type: Task
> Components: agent, master
> Reporter: Benjamin Bannier
> Assignee: Benjamin Bannier
> Labels: mesosphere
>
> To support speculative application of certain offer operations we have added resource versions to offer operation messages. This permits checking compatibility of master and agent state before applying operations.
> Launch operations are not modelled with offer operation messages, but instead with {{RunTaskMessage}}. In order to provide the same consistency guarantees we need to add resource versions to {{RunTaskMessage}} as well. Otherwise we would only rely on resource containment checks in the agent to catch inconsistencies; these can be unreliable as there is no guarantee that the matched agent resource is unique (e.g., with two {{RESERVE}} operations on similar resorces triggered on the same agent and one of these failing, the other succeeding, we would end up potentially sending one framework a success status and the other a failed one, but would not do anything the make sure the speculative operation application matches the resources belonging to the sent offer operation status update).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)