Return-Path: X-Original-To: apmail-accumulo-user-archive@www.apache.org Delivered-To: apmail-accumulo-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B1EAA10B2D for ; Wed, 1 May 2013 20:13:26 +0000 (UTC) Received: (qmail 54839 invoked by uid 500); 1 May 2013 20:13:26 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 54736 invoked by uid 500); 1 May 2013 20:13:26 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 54727 invoked by uid 99); 1 May 2013 20:13:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 May 2013 20:13:26 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of eric.newton@gmail.com designates 209.85.212.51 as permitted sender) Received: from [209.85.212.51] (HELO mail-vb0-f51.google.com) (209.85.212.51) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 May 2013 20:13:21 +0000 Received: by mail-vb0-f51.google.com with SMTP id x16so1479798vbf.38 for ; Wed, 01 May 2013 13:13:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=aIML7+EmJ9JIJQPrX2lhNm1dOWYDpDI269JkmsoBRJQ=; b=ci3Xgs5xvqxw9u2RfJLrBqF4pLd2CaSRwVrg0tL8NdmsU6hInOe+KmfXnqTn1QisD8 4Adi7B/zZ5b3djj1EcLpJulXd5aIGHvonGxPFBAN65apGWAU+fsxdd8vZL5oC6Kwad39 8twqqfefaOsJxBGf54kaDPwY7skLSH8z+HjZhZ8sDfAMC0XHcNG3zc7Lr6lspxDF8CFi gBMZPx7icelX2SvuktFXiFgu+gylBTpZ0CCaMFGGxTd8/WNfFWyRsNdfuiyZDdlSW5K/ /WWDLsofcJBw9QGSPXMkcrRJ9pPdVMu3BKTwiwKLLWhZZLPaFUmxcLZNNNpfgKAFtT4r nzuw== MIME-Version: 1.0 X-Received: by 10.52.20.210 with SMTP id p18mr1068508vde.42.1367439180560; Wed, 01 May 2013 13:13:00 -0700 (PDT) Received: by 10.58.207.234 with HTTP; Wed, 1 May 2013 13:13:00 -0700 (PDT) In-Reply-To: References: Date: Wed, 1 May 2013 16:13:00 -0400 Message-ID: Subject: Re: Newbie question: where do the services live? From: Eric Newton To: "user@accumulo.apache.org" Content-Type: multipart/alternative; boundary=20cf307d07509c400704dbadbeef X-Virus-Checked: Checked by ClamAV on apache.org --20cf307d07509c400704dbadbeef Content-Type: text/plain; charset=ISO-8859-1 On all but the largest clusters, the computing needs of the master/gc/monitor/tracer can all run on one node and can be co-located with a zookeeper server. Strictly speaking, you don't need a tracer. Unless you are running a very large cluster, one tracer will be enough. The tracer can be used to identify components that are performing slowly, so it needs to run all the time. -Eric On Wed, May 1, 2013 at 3:57 PM, Aaron G wrote: > Generic/best practices question about the 6 services: master, gc, > tserver, logger, monitor, tracer > > For this example/discussion let's say I have a cluster, with 10 nodes > (n01-n10)...3 of the nodes running zookeeper > > n01: NameNode, zooKeeper > n02: SecondaryNameNode, zooKeeper > n03: JobTracker, zooKeeper > n04: empty (for now) > > Let's label these storage/compute nodes: > n05-n10: dataNode, taskTracker > > So, how i thought this could be setup for Accumulo services: > > n04: master & gc > n05-n10: each runs a tserver & logger > > I think my main questions revolve around the monitor & tracer services and > where they run: > > 1. Does those need to run on every "compute node"? > 2. Do you only need one running instance of monitor? Perhaps on the n04? > Or does it need to run on every tserver as well? > 3. Do you only need the tracer service running on compute nodes? Or > everywhere (master & gc included)? Do you only need the tracer for the > purpose of development of Iterators, Scanners, Writers? They primarily > there to help with that activity? Or are they useful to have running "all > the time?" > > Thanks in advance, > Aaron > --20cf307d07509c400704dbadbeef Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On all but the largest clusters, the computing needs of th= e master/gc/monitor/tracer can all run on one node and can be co-located wi= th a zookeeper server.

Strictly speaking, you don't = need a tracer. =A0Unless you are running a very large cluster, one tracer w= ill be enough.

The tracer can be used to identify components tha= t are performing slowly, so it needs to run all the time.

-Eric


On Wed, May 1, 2013 at 3:57 PM, Aaron G = <aarongmldt@gmail.com> wrote:
Generic/best practices question about the 6 services: =A0m= aster, gc, tserver, logger, monitor, tracer

For this exa= mple/discussion let's say I have a cluster, with 10 nodes (n01-n10)...3= of the nodes running zookeeper

n01: =A0NameNode, zooKeeper
n02: =A0Secondary= NameNode, zooKeeper
n03: =A0JobTracker, zooKeeper
n04: = =A0empty (for now)

Let's label these storage/compute nodes:
n05-n10: =A0dat= aNode, taskTracker

So, how i thought this could be= setup for Accumulo services:

n04: =A0master & gc
n05-n10: =A0each runs a tserver & log= ger

I think my main questions revolve around the m= onitor & tracer services and where they run: =A0

1. =A0Does those need to run on every "compute node&quo= t;?=A0
2. =A0Do you only need one running instance of monitor? = =A0Perhaps on the n04? =A0Or does it need to run on every tserver as well?<= /div>
3. =A0Do you only need the tracer service running on compute nodes? = =A0Or everywhere (master & gc included)? =A0Do you only need the tracer= for the purpose of development of Iterators, Scanners, Writers? =A0They pr= imarily there to help with that activity? =A0Or are they useful to have run= ning "all the time?" =A0

Thanks in advance,
Aaron

--20cf307d07509c400704dbadbeef--