You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Sathya Hariesh (JIRA)" <ji...@apache.org> on 2013/03/14 02:29:11 UTC

[jira] [Updated] (MESOS-390) Slave should support file:/// URIs for executor path

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

Sathya Hariesh updated MESOS-390:
---------------------------------

    Description: 
The slave rejects executor paths sent by the framework that start with "file:///"

Related slave log,

Fetching resource file:///usr/local/bin/executor
A relative path was passed for the resource, but the configuration option frameworks_home is not set. Please either specify this config option or avoid using a relative path
Failed to fetch executors
Error setting up executor

  was:
The slave rejects executor paths sent by the framework that start with "file:///"

Related slave log,

{noformat}
Fetching resource file:///usr/local/bin/executor
A relative path was passed for the resource, but the configuration option frameworks_home is not set. Please either specify this config option or avoid using a relative path
Failed to fetch executors
Error setting up executor
{noformat}

    
> Slave should support file:/// URIs for executor path
> ----------------------------------------------------
>
>                 Key: MESOS-390
>                 URL: https://issues.apache.org/jira/browse/MESOS-390
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Sathya Hariesh
>
> The slave rejects executor paths sent by the framework that start with "file:///"
> Related slave log,
> Fetching resource file:///usr/local/bin/executor
> A relative path was passed for the resource, but the configuration option frameworks_home is not set. Please either specify this config option or avoid using a relative path
> Failed to fetch executors
> Error setting up executor

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira