Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <425251037.1213873186492.JavaMail.jira@brutus>
Date: Thu, 19 Jun 2008 03:59:46 -0700 (PDT)
From: "Hemanth Yamijala (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-3505) omissions in HOD documentation
In-Reply-To: <555382381.1212703725158.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hemanth Yamijala updated HADOOP-3505:
-------------------------------------

    Assignee: Vinod Kumar Vavilapalli  (was: Hemanth Yamijala)

> omissions in HOD documentation
> ------------------------------
>
>                 Key: HADOOP-3505
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3505
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/hod, documentation
>            Reporter: Ari Rabkin
>            Assignee: Vinod Kumar Vavilapalli
>            Priority: Blocker
>             Fix For: 0.18.0
>
>
> There's a couple HOD limitations that really trip up the unwary.
> Two I've encountered are that  hod can't take relative paths on the command line, and that if you pass hod a tarball with a modified /conf, then the cluster will fail mysteriously to be initialized.
> I don't see any references to either in the documentation, and it'd be great to write this down.

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