[
https://issues.apache.org/jira/browse/MESOS-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905481#comment-14905481
]
Adam B commented on MESOS-3421:
-------------------------------
Sharing resources could apply to general (non-persistent) disk resources, as
well as other custom resource types. I'd suggest we don't restrict the design
to just support sharing for persistent volumes. We'll also need to consider the
implications of "shared resources" on the allocator algorithm and the offer
model. Should these resources always be offered to every registered framework
(under that role), or just to one at a time? How is the upcoming quota feature
impacted? If a globally shared resource is then reserved for a particular role,
does that mean it can no longer be used by frameworks in other roles?
Let's also consider the implication of "sharing" when the volumes are external
to the node, for example tasks on two different nodes accessing the same NFS
mount.
I don't know if I have the time to shepherd this myself, but I'm definitely
interested in being involved in the design doc/discussion.
> Support sharing persistent volumes across task instances
> --------------------------------------------------------
>
> Key: MESOS-3421
> URL: https://issues.apache.org/jira/browse/MESOS-3421
> Project: Mesos
> Issue Type: Improvement
> Components: general
> Affects Versions: 0.23.0
> Reporter: Anindya Sinha
> Assignee: Anindya Sinha
>
> A service that needs persistent volume needs to have access to the same
> persistent volume (RW) from multiple task(s) instances on the same agent
> node. Currently, a persistent volume once offered to the framework(s) can be
> scheduled to a task and until that tasks terminates, that persistent volume
> cannot be used by another task.
> Explore providing the capability of sharing persistent volumes across task
> instances scheduled on a single agent node.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
