You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Tom Arnfeld (JIRA)" <ji...@apache.org> on 2014/05/22 17:55:02 UTC

[jira] [Assigned] (MESOS-1405) Mesos fetcher does not support S3(n)

     [ https://issues.apache.org/jira/browse/MESOS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Arnfeld reassigned MESOS-1405:
----------------------------------

    Assignee: Tom Arnfeld

> Mesos fetcher does not support S3(n)
> ------------------------------------
>
>                 Key: MESOS-1405
>                 URL: https://issues.apache.org/jira/browse/MESOS-1405
>             Project: Mesos
>          Issue Type: Improvement
>    Affects Versions: 0.18.2
>            Reporter: Tom Arnfeld
>            Assignee: Tom Arnfeld
>            Priority: Minor
>
> The HDFS client is able to support both S3 and S3N. Details for the difference between the two can be found here: http://wiki.apache.org/hadoop/AmazonS3.
> Examples:
> s3://bucket/path.tar.gz <- S3 Block Store
> s3n://bucket/path.tar.gz <- S3 K/V Store
> Either we can simply pass these URIs through to the HDFS client (hdfs.cpp) and let hadoop do the work, or we can integrate with S3 directly. The latter then requires we have a way of managing S3 credentials, whereas using the HDFS client will just pull credentials from HADOOP_HOME.



--
This message was sent by Atlassian JIRA
(v6.2#6252)