[
https://issues.apache.org/jira/browse/MESOS-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233191#comment-15233191
]
Jie Yu commented on MESOS-4828:
-------------------------------
Glad to see this committed! I am curious any reason the isolator is named as
"xfs/disk"?
Would 'disk/xfs' be better? I imagine we could have: 'disk/xfs', 'disk/du'
('posix/disk' is an alias of that to be backwards compatible), 'disk/zfs'...
> 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.4#6332)
