You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2008/03/24 18:47:24 UTC

[jira] Updated: (HADOOP-2855) [HOD] HOD fails to allocate a cluster if the tarball specified is a relative path

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

Vinod Kumar Vavilapalli updated HADOOP-2855:
--------------------------------------------

    Attachment: HADOOP-2855

Earlier behavior was not to normalize any paths(files or directories), so relative paths weren't getting expanded. Changed that behavior now. Tested with relative paths for ringmaster.hadoop-tar-ball, hod.script and hod.clusterdir.

Also added a new data type uri. Ringmaster.hadoop-tar-ball is changed to be of this data type.  So, a URI of the format file:// can be used to denote a path on the local file system. hodring.log-destination-uri also needs to changed to use this data type. Will file a jira for that.

Attaching patch.

> [HOD] HOD fails to allocate a cluster if the tarball specified is a relative path
> ---------------------------------------------------------------------------------
>
>                 Key: HADOOP-2855
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2855
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/hod
>    Affects Versions: 0.16.0
>            Reporter: Hemanth Yamijala
>            Assignee: Vinod Kumar Vavilapalli
>             Fix For: 0.17.0
>
>         Attachments: HADOOP-2855
>
>
> Run hod -t my-tar.tar.gz -o "allocate hod-cluster 3". Ringmaster fails to come up. The log shows the exception as an invalid URL for the tarball file. Basically HOD should translate the relative path to an absolute path and send it to the ringmaster.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.