accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ravi Mutyala <r...@hortonworks.com>
Subject Re: Accumulo 1.6.0 HA namenode testing
Date Wed, 18 Dec 2013 04:52:45 GMT
Do you mean a federated cluster? Different namenodes that share the same
datanodes.


On Tue, Dec 17, 2013 at 10:44 PM, Keith Turner <keith@deenlo.com> wrote:

> On Tue, Dec 17, 2013 at 11:39 PM, Josh Elser <josh.elser@gmail.com> wrote:
>
> > I've been running CI tests against 1.5.1 with HA (QJM) Namenode support
> > for a few weeks now. Earlier this week I started running the same against
> > 1.6.0.
> >
> > AFAICT, everything has been fine so far. This is with the
> > hdfs-agitation.pl (causing a failover using the haadmin command every
> ten
> > minutes) script that Sean provided a while back.
> >
> >
> I was not using the correct terminology for what I was thinking, but I am
> not sure what the correct terminology is.  I do not want to be limited by
> the memory of one machine for hdfs metadata and I want HA.  So would it be
> correct to say that I want to test with multiple HA nameservices?   For
> example test 1.6 w/ three nameservices, where each nameservice has two HA
> namenodes.   This would allow hdfs metadata to spread across the memory of
> three machines.
>
>
> >
> > On 12/17/13, 11:32 PM, Keith Turner wrote:
> >
> >> Has anyone has done any HA namenode testing w/ 1.6.0?
> >>
> >> I have started poking at viewfs:// w/ two regular namenodes and have
> been
> >> finding issues.   I want to eventually run the test suite against
> Accumulo
> >> 1.6.0 w/ multiple HA namenodes.
> >>
> >>
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message