accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <bus...@clouderagovt.com>
Subject Re: Accumulo 1.6.0 HA namenode testing
Date Wed, 18 Dec 2013 05:04:40 GMT
On Dec 18, 2013 12:00 AM, "Keith Turner" <keith@deenlo.com> wrote:
>
> On Tue, Dec 17, 2013 at 11:52 PM, Sean Busbey <busbey+ml@clouderagovt.com
>wrote:
>
> > 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 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.
> > >
> > >
> > These HDFS nameservices are independent HDFS instances using the new
> > span-HDFS-instances feature in Accumulo 1.6? Or they are nameservices
using
> > HDFS federation across HA pairs?
> >
>
> HDFS federation across HA pairs, describes what I am thinking.   I did
want
> the HA pairs to share datanodes as Ravi mentioned.  So I would like to
test
> w/ 2 or more federated HA pairs.
>
>

Yeah, that's a supported configuration of HDFS federation with HA. HDFS
Federation always shares datanodes.

I've done some testing on earlier versions with HA as Josh described.
Nothing with Federation yet.

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