Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: pass (athena.apache.org: domain of mdrob@cloudera.com designates
 209.85.214.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADxc9BkQ2m_idcqV1NhGTWOw-ASSXjrv4Fi87N-cUUm=oybRjA@mail.gmail.com>
References: 
 <CADxc9BkQ2m_idcqV1NhGTWOw-ASSXjrv4Fi87N-cUUm=oybRjA@mail.gmail.com>
From: Mike Drob <madrob@cloudera.com>
Date: Fri, 14 Mar 2014 15:28:33 -0400
Message-ID: 
 <CAFAMeYLt+doDadLeX95wzmS=USC2Qky+0d8xFrerKs7b-tqttw@mail.gmail.com>
Subject: Re: HA namenode questions
To: dev@accumulo.apache.org
Content-Type: multipart/alternative; boundary=089e0118254490149304f496140c

--089e0118254490149304f496140c
Content-Type: text/plain; charset=ISO-8859-1

Specifically, for dealing with a large number of clients, you can use
ZooKeeper Observers.

---------- Forwarded message ----------
From: Eric Newton <eric.newton@gmail.com>
Date: Fri, Mar 14, 2014 at 3:18 PM
Subject: HA namenode questions
To: dev@accumulo.apache.org


For those of you running HA NN on large clusters, I'm looking for some
advice.

I was looking at an HA NN config today.  Either by default, or by following
the configuration instructions, I saw that the zookeeper timeout was set to
5 seconds.

* is this a reasonable timeout?
* do you provide HA NN its own set of zookeepers?

We have seen problems with large GC pauses with tablet servers.  This
happens less and less as we have learned more tricks, but I'm constantly
talking to users who want their zookeeper timeout as high as two minutes.

We have also had to increase the number of zookeepers on our largest
clusters in order to handle the "thundering herd" load when large
map/reduce jobs kick off and they all start talking to accumulo, which
requires reading information from zookeeper.

Any experience you can share about HA NN configuration at scales over few
hundred nodes would be appreciated.

-Eric

--089e0118254490149304f496140c--