You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Krystian Nowak (JIRA)" <ji...@apache.org> on 2016/09/13 16:10:20 UTC

[jira] [Commented] (MESOS-3367) Mesos fetcher does not extract archives for URI with parameters

    [ https://issues.apache.org/jira/browse/MESOS-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487619#comment-15487619 ] 

Krystian Nowak commented on MESOS-3367:
---------------------------------------

[~haosdent@gmail.com] Should it also already be working in DCOS when e.g. having Spark submit issued with jar to be fetched from S3 using signed S3 URL like https://mybucket.s3.amazonaws.com/myjar.jar?AWSAccessKeyId=MYKEY&Expires=1473776407&Signature=MYSIGNATURE ?

Currently I am getting stuck with:
{noformat}/bin/sh: 1: 30: not found{noformat}
probably due to the fact that params get generated like this:
{noformat}... $MESOS_SANDBOX/myjar.jar?AWSAccessKeyId=MYKEY&Expires=1473776407&Signature=MYSIGNATURE ...{noformat}

> Mesos fetcher does not extract archives for URI with parameters
> ---------------------------------------------------------------
>
>                 Key: MESOS-3367
>                 URL: https://issues.apache.org/jira/browse/MESOS-3367
>             Project: Mesos
>          Issue Type: Improvement
>          Components: fetcher
>    Affects Versions: 0.22.1, 0.23.0
>         Environment: DCOS 1.1
>            Reporter: Renat Zubairov
>            Assignee: haosdent
>            Priority: Minor
>              Labels: mesosphere
>
> I'm deploying using marathon applications with sources served from S3. I'm using a signed URL to give only temporary access to the S3 resources, so URL of the resource have some query parameters.
> So URI is 'https://foo.com/file.tgz?hasi' and fetcher stores it in the file with the name 'file.tgz?hasi', then it thinks that extension 'hasi' is not tgz hence extraction is skipped, despite the fact that MIME Type of the HTTP resource is 'application/x-tar'.
> Workaround - add additional parameter like '&workaround=.tgz'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)