mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joseph Wu <>
Subject Re: Review Request 69960: Added the concept of "orphaned operations" to the master.
Date Fri, 22 Feb 2019 00:06:24 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated Feb. 21, 2019, 4:06 p.m.)

Review request for mesos, Benno Evers, Gastón Kleiman, and Greg Mann.


* Reworded/reworked some comments based on various changes made to the chain over the last
few revisions.
* When removing a framework, terminal operations are also marked as orphans now.
* Added a critical section to the allocator when removing a framework and its operations.
* Added a log message when orphaning an operation.

Bugs: MESOS-9542

Repository: mesos

Description (updated)

An orphaned operation is a non-speculative operation whose
originating framework is unknown.  These operations will consume
resources until they are terminated, but will have no entry
in the allocator because their associated framework does not exist.

To account for resources used by orphaned operations, the operation's
resources are removed from the agent's total resources upon being

This commit handles one of the two possible code paths which can
introduce orphaned operations.

Diffs (updated)

  src/master/master.hpp ccd117f607747d49e5259d9ba6645fed61811adf 
  src/master/master.cpp 106d924bf16231b3bda3fb719db68c01d73644ee 




See last patch in chain.


Joseph Wu

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message