You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Benno Evers (JIRA)" <ji...@apache.org> on 2019/03/12 18:05:00 UTC

[jira] [Created] (MESOS-9650) Document the semantics of operation pipelining

Benno Evers created MESOS-9650:
----------------------------------

             Summary: Document the semantics of operation pipelining
                 Key: MESOS-9650
                 URL: https://issues.apache.org/jira/browse/MESOS-9650
             Project: Mesos
          Issue Type: Improvement
            Reporter: Benno Evers


In our `Accept` protobuf, frameworks can specify multiple offer operations that are to be executed on the received offer:

https://github.com/apache/mesos/blob/40abcefab4f2887e61786365b46bc22155a2d1ff/include/mesos/scheduler/scheduler.proto#L317

However, the semantics of specifying multiple operations in this way are currently not documented anywhere I could find, except for a comment on that protobuf that the master will be "performing the specified operations in a sequential manner."

In particular, it is unclear what will happen if any operation in the sequence fails, or at which particular points during the operation the master will move on to the next (i.e. if we have [RESERVE, LAUNCH, RESERVE], when exactly does the second reserve happen), and if there are any restrictions on combining operations in this way.

While all of this can be figured out by reading the master source code, we should add some user-facing documentation about this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)