[
https://issues.apache.org/jira/browse/MESOS-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam B updated MESOS-2731:
--------------------------
Description:
Certain storage options require storage drivers to access them including HDFS
driver, Quobyte client, Database driver, and so on.
When Tasks in Mesos require access to such storage they also need access to the
respective driver on the node where they were scheduled to.
As it is not desirable to deploy the driver onto all nodes in the cluster, it
would be good to deploy the driver on demand.
Use Cases:
1. Fetcher Cache pulling resources from user-provided URIs
2. Framework executors/tasks requiring r/w access to HDFS/DFS
3. Framework executors/tasks requiring r/w Databases access (requiring drivers)
was:
Certain storage options require storage drivers to access them including HDFS
driver, Quobyte client, Database driver, and so on.
When Tasks in Mesos require access to such storage they also need access to the
respective driver on the node where they were scheduled to.
As it is not desirable to deploy the driver onto all nodes in the cluster, it
would be good to deploy the driver on demand.
Use Cases:
1. Fetcher Cache accessing resources from user-provided URIs
2. Framework executors/tasks requiring access to HDFS/DFS
3. Framework executors/tasks requiring Databases access (requiring drivers)
> Allow frameworks to deploy storage drivers on demand.
> -----------------------------------------------------
>
> Key: MESOS-2731
> URL: https://issues.apache.org/jira/browse/MESOS-2731
> Project: Mesos
> Issue Type: Epic
> Reporter: Joerg Schad
> Labels: mesosphere
>
> Certain storage options require storage drivers to access them including HDFS
> driver, Quobyte client, Database driver, and so on.
> When Tasks in Mesos require access to such storage they also need access to
> the respective driver on the node where they were scheduled to.
> As it is not desirable to deploy the driver onto all nodes in the cluster, it
> would be good to deploy the driver on demand.
> Use Cases:
> 1. Fetcher Cache pulling resources from user-provided URIs
> 2. Framework executors/tasks requiring r/w access to HDFS/DFS
> 3. Framework executors/tasks requiring r/w Databases access (requiring
> drivers)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
