mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Qian Zhang <>
Subject Re: Review Request 64978: Made task's volume directory visible in the /files endpoints.
Date Mon, 15 Jan 2018 06:21:36 GMT

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

(Updated Jan. 15, 2018, 2:21 p.m.)

Review request for mesos, Benjamin Mahler, Gilbert Song, Jie Yu, and Vinod Kone.


Addressed comments.

Bugs: MESOS-8279

Repository: mesos


In MESOS-7225, we made a task can access any volumes specified in its
disk resources from its own sandbox by introducing a workaround to the
default executor, i.e., add a `SANDBOX_PATH` volume with type `PARENT`
to the corresponding nested container. It will be translated into a bind
mount in the nested container's mount namespace, thus not visible in the
host mount namespace, that means the task's volume directory can not be
visible in Mesos UI since it operates in the host mount namespace.

In this patch, to make the task's volume directory visible in Mesos UI,
we attached the executor's volume directory to it, so when users browse
task's volume directory in Mesos UI, what they actually browse is the
executor's volume directory. Note when calling `Files::attach()`, the
third argument `authorized` is not specified, that is because it is
already specified when we do the attach for the executor's sandbox and
it is also applied to the executor's tasks.

Diffs (updated)

  src/slave/slave.hpp ef0eae21af811cc09f43cd1d4c4ccc0c33cbeb39 
  src/slave/slave.cpp aeb0fdaeda78f26de2ec790735bfa88c5be72850 




sudo make check


Qian Zhang

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