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 1354AC8D8 for ; Fri, 4 May 2012 17:51:05 +0000 (UTC) Received: (qmail 65438 invoked by uid 500); 4 May 2012 17:51:04 -0000 Delivered-To: apmail-incubator-bigtop-dev-archive@incubator.apache.org Received: (qmail 65385 invoked by uid 500); 4 May 2012 17:51:04 -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 65377 invoked by uid 99); 4 May 2012 17:51:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 May 2012 17:51:04 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of shaposhnik@gmail.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bk0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 May 2012 17:50:58 +0000 Received: by bkcjm2 with SMTP id jm2so2643055bkc.6 for ; Fri, 04 May 2012 10:50:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=rTVzH1CY0vyzdG3rbS45VHgGfTuJ2vZiNOOyHmsWHM4=; b=vN2dXqyPWgRgOYvsF1kvY0eE90fYUjnghtoHfnvaDsJ14qts/ZUQOw5rEFPgh8BPBh /oIe3H0QCoLhH48XO63CJAnDl+rjHTax5NPv9R0enwVrlhaY0OBIAxC1j72raxRBwKSg Xo3Zx0j9YlTTg17QYW0S+YcF7t9XS8TiAsvB5b3EpOssEBbrDm4YqI7Hg3oxz9HsmwlZ 2t1AImYUNnU43k0n2dzC1DAFSAkhFVS3Lfn3s6fhYBtdD7kZF0IhgK3yqDmvpqCI+H8A jQrbrbn3A6yIq4s+WwvInbTA6oXzyekyWozivqlXVEutDyLBf9DbRnHXnXn1ll2MFWRE LC3A== MIME-Version: 1.0 Received: by 10.204.132.87 with SMTP id a23mr2201897bkt.134.1336153837260; Fri, 04 May 2012 10:50:37 -0700 (PDT) Sender: shaposhnik@gmail.com Received: by 10.204.230.207 with HTTP; Fri, 4 May 2012 10:50:37 -0700 (PDT) Date: Fri, 4 May 2012 10:50:37 -0700 X-Google-Sender-Auth: rFp95cOnyuj7D0lAg6EinIl3zQs Message-ID: Subject: Hama in Bigtop From: Roman Shaposhnik To: bigtop-dev@incubator.apache.org Cc: edwardyoon@apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I'm really happy to see that Haman integration into Bigtop is making very steady progress. In fact today, for the first time, I was able to build packages for Hama and play with it (thanks to Victor!). That, of course, made me curious about a couple of things wrt. to Hama deployment/usage. I'm CCign Edward for his advice (Edward, feel free to CC hama mailing list if you think its appropriate). So, here's what I'm curious about: * What does Hama *really* depend on in Hadoop? It seems that given its architecture the only dependency should be on HDFS (since it essentially replaces Mapreduce layer) and common. * I see that there's a way of running hama's own Zookeeper service. Is there a way to utilize an existing instance of Zookeeper? * Hama on YARN -- does it still need its own services running (BSPmater, Groom) or does it become a 100% the same type of application that mapreduce is on top of YARN ? * What's the best way to run as many 'example' BSP jobs as possible? Is there an equivalent of hadoop-examples.jar ? Thanks, Roman.