mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-4828) XFS disk quota isolator
Date Fri, 10 Feb 2017 08:14:42 GMT

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

Adam B commented on MESOS-4828:
-------------------------------

Looks like the bulk of this Epic was completed 10 months ago, so it's not reasonable to call
it out in the 1.2.0 CHANGELOG, and the work is ongoing, so I'm just going to remove the targetVersion,
and you can set the fixVersion whenever you do resolve the Epic.

> XFS disk quota isolator
> -----------------------
>
>                 Key: MESOS-4828
>                 URL: https://issues.apache.org/jira/browse/MESOS-4828
>             Project: Mesos
>          Issue Type: Epic
>          Components: isolation
>            Reporter: James Peach
>            Assignee: James Peach
>
> Implement a disk resource isolator using XFS project quotas. Compared to the {{posix/disk}}
isolator, this doesn't need to scan the filesystem periodically, and applications receive
a {{EDQUOT}} error instead of being summarily killed.
> This initial implementation only isolates sandbox directory resources, since isolation
doesn't have any visibility into the the lifecycle of volumes, which is needed to assign and
track project IDs.
> The build dependencies for this are XFS header (from xfsprogs-devel) and libblkid. We
need libblkid or the equivalent to map filesystem paths to block devices in order to apply
quota.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message