[
https://issues.apache.org/jira/browse/MESOS-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933692#comment-14933692
]
Jie Yu commented on MESOS-3421:
-------------------------------
Glad to see the discussion here! I agree with [~adam-mesos] that the concept of
"shared" resources should be applicable to other types of resources as well.
Here are a list of issues I can think of that we need to address:
1) ownership? For instance, disk resource, which executor/task has the write
permission (i.e., 1 writer + multiple readers)?
2) what if the limit of the resource has been reached? Do we kill all tasks
using it? Or just the owner?
3) reference counting? Do we need to track how many tasks/executors are still
using the resource so that it cannot be released?
4) permission (e.g., group/owner)? This is specific for disk resources.
We definitely need to change the allocator accordingly so that 'shared'
resources can be allocated to multiple fraemworks currently.
> 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)
