You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Elizabeth Lingg (JIRA)" <ji...@apache.org> on 2016/04/18 20:24:25 UTC

[jira] [Commented] (MESOS-5196) Sandbox GC shouldn't return early in the face of an error.

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

Elizabeth Lingg commented on MESOS-5196:
----------------------------------------

+1, Let's clean up everything we can in the sandbox. For example if GC encounters an immutable file or file owned by another user (other than the task user) or another error, we should log an error and skip that particular file and continue with GC instead of exiting.

> Sandbox GC shouldn't return early in the face of an error.
> ----------------------------------------------------------
>
>                 Key: MESOS-5196
>                 URL: https://issues.apache.org/jira/browse/MESOS-5196
>             Project: Mesos
>          Issue Type: Bug
>          Components: slave
>            Reporter: Yan Xu
>            Assignee: Megha
>
> Since GC's purpose is to clean up stuff that no one cares about anymore, it should do its best to recover as much as disk space possible.
> In practice it's not easy for GC to anticipate what the task has done to the sandbox in a generic manner, e.g., immutable file attribute, mount points, etc. The least it can do is to log the error and continue with the rest of the files in the sandbox.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)