[
https://issues.apache.org/jira/browse/FLINK-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900829#comment-15900829
]
ASF GitHub Bot commented on FLINK-5975:
---------------------------------------
Github user addisonj commented on the issue:
https://github.com/apache/flink/pull/3481
Okay, just moved things around, agree that its a better place, but was
hesitant at first as we were building any other mesos objects earlier.
Hopefully this still works. I think going forwad and adding support for other
container options, such as additional network ports, additional URIs to
download, that would be a better place to put them.
Also, I have one other small commit, it wasn't because the volume info
wasn't getting attached soon enough.
This now is working for me in my dev env, which is 1.2.0 with these patches
applied
> Mesos should support adding volumes to launched taskManagers
> ------------------------------------------------------------
>
> Key: FLINK-5975
> URL: https://issues.apache.org/jira/browse/FLINK-5975
> Project: Flink
> Issue Type: Improvement
> Components: Mesos
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Addison Higham
> Priority: Minor
>
> Flink needs access to shared storage.
> In many cases, this is HDFS, but it would be nice to also support file URIs
> on an mounted NFS for example.
> Mesos exposes APIs for adding volumes, so it should be relatively simply to
> add this.
> As an example, here is the spark code for supporting volumes:
> https://github.com/apache/spark/blob/master/resource-managers/mesos/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala#L35
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
