[
https://issues.apache.org/jira/browse/MESOS-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908243#comment-14908243
]
Anindya Sinha commented on MESOS-3421:
--------------------------------------
> 1.) prvoide a way for user to publish data's location/info
Currently, the container_path is specified in the Offer::Operation::CREATE
through the Volumes section of the protobuf (within DiskInfo). This is the path
within the container, which is linked to physical volume (currently set in
<work_dir>/volumes/roles/<role>/<persistence-id>).
Are you suggesting that the container_path should be set when LAUNCH happens as
opposed to when CREATE happens? I think that might be a good enhancement to
enable each task container specify its own container_path.
> 2.) provide a way for user to share volume in slave hosts
I think just because the framework picks up a persistent volume from the offer
to schedule a task should be good to demonstrate an intention to use a volume -
shared or non-shared.
> 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)
