You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Dominic Hamon (JIRA)" <ji...@apache.org> on 2014/10/06 23:05:36 UTC
[jira] [Updated] (MESOS-1586) Isolate system directories, e.g.,
per-container /tmp
[ https://issues.apache.org/jira/browse/MESOS-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominic Hamon updated MESOS-1586:
---------------------------------
Sprint: Q3 Sprint 1, Q3 Sprint 2, Q3 Sprint 3, Q3 Sprint 4, Mesos Q3 Sprint 5, Mesos Q3 Sprint 6, Mesos Q3 Sprint 7 (was: Q3 Sprint 1, Q3 Sprint 2, Q3 Sprint 3, Q3 Sprint 4, Mesos Q3 Sprint 5, Mesos Q3 Sprint 6)
> Isolate system directories, e.g., per-container /tmp
> ----------------------------------------------------
>
> Key: MESOS-1586
> URL: https://issues.apache.org/jira/browse/MESOS-1586
> Project: Mesos
> Issue Type: Improvement
> Components: isolation
> Affects Versions: 0.20.0
> Reporter: Ian Downes
> Assignee: Ian Downes
>
> Ideally, tasks should not write outside their sandbox (executor work directory) but pragmatically they may need to write to /tmp, /var/tmp, or some other directory.
> 1) We should include any such files in disk usage and quota.
> 2) We should make these "shared" directories private, i.e., each container has their own.
> 3) We should make the lifetime of any such files the same as the executor work directory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)