Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 95777 invoked from network); 14 Feb 2011 06:16:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Feb 2011 06:16:29 -0000 Received: (qmail 24015 invoked by uid 500); 14 Feb 2011 06:16:28 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 23654 invoked by uid 500); 14 Feb 2011 06:16:24 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 23641 invoked by uid 99); 14 Feb 2011 06:16:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Feb 2011 06:16:23 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.145.54.171] (HELO mrout1.yahoo.com) (216.145.54.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Feb 2011 06:16:17 +0000 Received: from [10.66.72.163] (sightbusy-lx.eglbp.corp.yahoo.com [10.66.72.163]) by mrout1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p1E6FjXv032594; Sun, 13 Feb 2011 22:15:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=yahoo-inc.com; s=cobra; t=1297664146; bh=87jj+TVOEXmuqCxuxUzWgZ9org91LfYuptYNavggZAg=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=mn1digmGbnLU5TUTFA1ONARCJkZmeQWJxs+DizkEiVdC50pNMTnaZ8zMDpToWrbPs OoI6uG4SQWSIIZ0/RwDJ6kUV2kOjyV2inTjY9pWZvZ9rbEpOe2R4F6uA++EnTstqUG rdTYoF5v8FBi9iNrfg4rI7RjZxcmVkGzZGiuOaB0= Message-ID: <4D58C890.5030601@yahoo-inc.com> Date: Mon, 14 Feb 2011 11:45:44 +0530 From: Vinod KV User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: "general@hadoop.apache.org" CC: "Owen O'Malley" Subject: Re: [VOTE] Abandon hod Common contrib References: <84B97117-5DA4-4A32-912A-8DBFCE3D063E@linkedin.com> <535D05CA-3321-48BA-82C4-C18FC8983C3A@mac.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hemanth Yamijala and myself were the main contributors to HOD. Answers to few of the questions: - IIRC, Hod needed python 2.5 (or some such latest) which was not available on Hudson. The tests gracefully run only when that version is available. We always used to run these tests on dev boxes before pushing patches. May be the versions upgraded after that, but I am not sure. - HOD wasn't tested extensively with Hadoop 0.20 and beyond. But I could successfully run HOD clusters with Hadoop 20. Thing that could affect the run are the configuration properties, environment variables and the scripts which at that time were backwards compatible. If some properties were removed in 21/22 breaking compatibility with pre 20 versions (very much possible), that will warrant fixing HOD. Otherwise, things should work as they are. Sure would like to know any interest with the users. Thanks, +Vinod On Saturday 12 February 2011 10:45 AM, Owen O'Malley wrote: > On Feb 11, 2011, at 6:17 PM, Nigel Daley wrote: > >>> a) I don't think hod is actually part of any unit tests, so >>> including it would likely only be a burden on the tarball size. >> Not true. HOD has python unit tests and is the reason our builds >> have dependencies on python. > But Allen's point is that I don't recall ever seeing HOD test failures > causing the build to fail. > >>> b) The edu community uses this quite extensively, evidenced by the >>> topic coming up on the mailing lists at least once every two months >>> or so and has for years. Can't say that about the other contrib >>> modules other than the schedulers and streaming. >> Then they are using old version of Hadoop. AFAICT HOD does not work >> with 0.20 or beyond. > Out of curiosity, what goes wrong? Clearly nothing major has changed > in starting up a mapreduce cluster in a very long time. > >>> c) The community that does use it has even submitted a patch that >>> we've ignored. >> Which means the committers of this project gave up on it long ago. > There are also some patches on core Hadoop that have been sitting for > a long time, so I don't think that is a valid inference. > > I would love to hear some of the people who are using HOD speak up and > give us their feedback. > > -- Owen >