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/10/13 14:27:00 UTC

[jira] [Commented] (MESOS-8088) Introduce Lamport timestamp for offer operations.

    [ https://issues.apache.org/jira/browse/MESOS-8088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203627#comment-16203627 ] 

Benjamin Bannier commented on MESOS-8088:
-----------------------------------------

It might be possible to introduce this by adding tooling working with {{TimeInfo}}.

> Introduce Lamport timestamp for offer operations.
> -------------------------------------------------
>
>                 Key: MESOS-8088
>                 URL: https://issues.apache.org/jira/browse/MESOS-8088
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Jie Yu
>
> We need to use Lamport clock (https://en.wikipedia.org/wiki/Lamport_timestamps) to establish partial ordering between offer operation, and the resources the operation is operating on.
> It is used to establish happens before relations so that RPs can reject those operations that applies to a stale snapshot of the resources due to speculation failures.
> See more details in this doc:
> https://docs.google.com/document/d/1RrrLVATZUyaURpEOeGjgxA6ccshuLo94G678IbL-Yco/edit#
> Given that the Lamport clock needs to be transferred between agent and masters, it needs to be serialized to protobuf. We probably needs to define the following methods for it:
> ```
> merge(...); // Take a max between the two.
> increment();
> operation<(...);
> copy and assignment operator
> ```



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)