[
https://issues.apache.org/jira/browse/MESOS-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944306#comment-14944306
]
Jie Yu commented on MESOS-3421:
-------------------------------
Thanks for discussion! I guess your main question is: besides disk resources,
is there any other use case for 'shared' resources. Some of the examples I can
think of are: shared memory
(http://man7.org/linux/man-pages/man7/shm_overview.7.html), GPU, etc.
> IIUC, shareable resources are relevant not for resource types, but when a
> discrete "thing" is associated with the resource type
That's a great observation! [~bmahler] also mentioned to me that a 'shared'
resource probably needs to have an identifier (e.g., the persistence id for
persistent volumes). For that, we can have a concept of 'sharable' resources.
Not every type of resources can be shared, they have to have some sort of
identifier so that it's a discrete/concrete "thing" that can be shared.
My biggest worry about introducing a 'shared' flag just for disk resources is
that we'll eventually end up implementing the same logic for other types of
sharable resources in the future, and we'll end up with a lot of DiskInfo
specific code in the allocator.
> 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)