Return-Path: X-Original-To: apmail-incubator-bigtop-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bigtop-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 059C1C80A for ; Wed, 2 May 2012 18:45:44 +0000 (UTC) Received: (qmail 69458 invoked by uid 500); 2 May 2012 18:45:43 -0000 Delivered-To: apmail-incubator-bigtop-dev-archive@incubator.apache.org Received: (qmail 69415 invoked by uid 500); 2 May 2012 18:45:43 -0000 Mailing-List: contact bigtop-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bigtop-dev@incubator.apache.org Delivered-To: mailing list bigtop-dev@incubator.apache.org Received: (qmail 69407 invoked by uid 99); 2 May 2012 18:45:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2012 18:45:43 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.217.175] (HELO mail-lb0-f175.google.com) (209.85.217.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2012 18:45:36 +0000 Received: by lbol5 with SMTP id l5so521712lbo.6 for ; Wed, 02 May 2012 11:45:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=4gEmo8CHF176qqDh4kWcVpYkgHRcbSO+wlrSIv4lmdo=; b=K3CucmIaPdr5MSFM7tu0Uf5PEOkf4r9oU5LgML209HL6/hUlc4+pQ22PyHjPEGU4L2 eFeT7w8m4KRkwsu+Bs+r5zrJSPGozFUhT9szPBq0/W76UEtFef89+JBNCMY7SwI/5VYh eD6swKs100YUMhvwReiBxMiTPA86WFr1OTmcuEJCnV5j+94xilgfJg5UEUxsijQ5LPZt AsA8UI8WWzMxiK0CZY4Bn01Vu5BbZ/jgrM40iHjd5Anq9tuTvB4lvVC24z1Eun4KrXxV WbDBr/xoyyzRUTFZqwYxsfwds91O49DRRSNMbwCF2jkPuGVkhgzR7MippRiYemlFVCBz QMSQ== Received: by 10.112.23.66 with SMTP id k2mr247888lbf.28.1335984314567; Wed, 02 May 2012 11:45:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.58.53 with HTTP; Wed, 2 May 2012 11:44:44 -0700 (PDT) In-Reply-To: References: From: Matt Foley Date: Wed, 2 May 2012 11:44:44 -0700 Message-ID: Subject: Re: Guarding against the use of upstream scripts To: bigtop-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=e0cb4efe2f2c7eccd204bf121662 X-Gm-Message-State: ALoCoQlmuh4+dPtk8Mnrm3lEw/z87QqCm29cYP2FAqFubCVIzO6KUJC6j9uVlZZkAVBp5HjC/CpB --e0cb4efe2f2c7eccd204bf121662 Content-Type: text/plain; charset=ISO-8859-1 What is the justification for saying "what we are doing in BigTop", when it is diverging from what has been done for years in the Components? It seems that this is carelessly discarding what is being practiced at a lot of sites, because you'd rather do it this way. Generally speaking, we make the Hadoop Ecosystem easier to use by adhering to familiar usage, rather than diverging. Please give reasons for the divergence. Thanks, --Matt On Wed, May 2, 2012 at 11:31 AM, Roman Shaposhnik wrote: > On Wed, May 2, 2012 at 11:01 AM, Owen O'Malley wrote: > > On Wed, May 2, 2012 at 8:34 AM, Roman Shaposhnik wrote: > >> Guys, > >> > >> I've noticed lately that new users of the Bigtop distro fall prey > >> to thinking that they can simply utilized upstream launcher scripts > >> as is by running them from under /usr/lib/bin > >> directories. Something this works. More often it doesn't. > > > > This will break users in two ways: > > Just to be clear (and sorry for not being specific in the original email): > this > only applies to trunk e.g. Hadoop 2.X based Bigtop. > > > 1. Many user scripts use $HADOOP_HOME/bin/X to find script X. > > Not sure I understand how this applies to Hadoop 2.X codeline. > HADOOP_HOME has been deprecated there and in fact now > that we have split the sub-projects it no longer makes even a > backward-compatibility sense to maintain the illusion. > > > 2. Until those scripts are available in other locations, there is no > > choice. For users that want to manage the servers manually, having > > access to the hadoop-daemon.sh is required. Of course, it should be in > > /usr/sbin/hadoop-daemon.sh, but until it is of course the users needs > > to reference it in $HADOOP_HOME/sbin/hadoop-daemon.sh. > > Right, but the Bigtop layout is completely different anyway. It has > very little to do with the upstream Hadoop 2.X layout. > > Please consider this in the context of what we are doing in Bigtop, > not what happens with upstream Hadoop. > > Thanks, > Roman. > --e0cb4efe2f2c7eccd204bf121662--