Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates
 209.85.215.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAOiuM-7Y8UfQ=612VaSLNo6sF6_yx9y0MEG9NmwnvNp6bwZe5Q@mail.gmail.com>
References: 
 <CAOiuM-4UMmLA7UHMp4hhjpLWUrHDxg1t4tN4aWvnZUMcTxG+KQ@mail.gmail.com>
	<CAAg3a2p0Br42bVJXfbySngiU4_+24P1Xww1YKQBHAt5i4T8oYg@mail.gmail.com>
	<CAOiuM-4pbf1VGvEVoTNps_pJ9jDPj8DBX4yjRLF5QB8yuC+hMA@mail.gmail.com>
	<CAOiuM-7Y8UfQ=612VaSLNo6sF6_yx9y0MEG9NmwnvNp6bwZe5Q@mail.gmail.com>
Date: Fri, 8 Nov 2013 14:33:21 -0800
Message-ID: 
 <CALte62wm1GMuvwGxCMKy1x08LYL5=4FHm=_dH8WN14xVs84i6A@mail.gmail.com>
Subject: Re: Setting up NxN replication
From: Ted Yu <yuzhihong@gmail.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=089e0115e7b439762104eab1f8b6

--089e0115e7b439762104eab1f8b6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Ishan:
In your use case, the same table is written to in 10 clusters at roughly
the same time ?

Please clarify.


On Fri, Nov 8, 2013 at 2:29 PM, Ishan Chhabra <ichhabra@rocketfuel.com>wrot=
e:

> @Demai,
> We actually have 10 clusters in different locations.
> The replication scope is not an issue for me since I have only one column
> family and we want it replicated to each location.
> Can you elaborate more on why a replication setup of more than 3-4 cluste=
rs
> would be a headache in your opinion?
>
>
> On Fri, Nov 8, 2013 at 2:16 PM, Ishan Chhabra <ichhabra@rocketfuel.com
> >wrote:
>
> > @Demai,
> > Writes from B should also go to A and C. So, if I were to continue on
> your
> > suggestion, I would setup A-B master master and B-C master-master, whic=
h
> is
> > what I was proposing in the 2nd approach (MST based).
> >
> > @Vladimir
> > That is classified. :P
> >
> >
> > On Fri, Nov 8, 2013 at 1:20 PM, Vladimir Rodionov <
> vladrodionov@gmail.com>wrote:
> >
> >> *I want to setup NxN replication i.e. N clusters each replicating to
> each
> >> other. N is expected to be around 10.*
> >>
> >> Preparing to thermonuclear war?
> >>
> >>
> >>
> >>
> >> On Fri, Nov 8, 2013 at 1:14 PM, Ishan Chhabra <ichhabra@rocketfuel.com
> >> >wrote:
> >>
> >> > I want to setup NxN replication i.e. N clusters each replicating to
> each
> >> > other. N is expected to be around 10.
> >> >
> >> > On doing some research, I realize it is possible after HBASE-7709 fi=
x,
> >> but
> >> > it would lead to much more data flowing in the system. eg.
> >> >
> >> > Lets say we have 3 clusters: A,B and C.
> >> > A new write to A will go to B and then C, and also go to C directly
> via
> >> the
> >> > direct path. This leads to unnecessary network usage and writes to W=
AL
> >> of
> >> > B, that should be avoided. Now imagine this with 10 clusters, it won=
=92t
> >> > scale.
> >> >
> >> > One option is to create a minimum spanning tree joining all the
> clusters
> >> > and make nodes replicate to their immediate peers in a master-master
> >> > fashion. This is much better than NxN mesh, but still has extra
> network
> >> and
> >> > WAL usage. It also suffers from a failure scenarios where the a sing=
le
> >> > cluster going down will pause replication to clusters downstream.
> >> >
> >> > What I really want is that the ReplicationSource should only forward
> >> > WALEdits with cluster-id same as the local cluster-id. This seems
> like a
> >> > straight forward patch to put in.
> >> >
> >> > Any thoughts on the suggested approach or alternatives?
> >> >
> >> > --
> >> > *Ishan Chhabra *| Rocket Scientist | RocketFuel Inc.
> >> >
> >>
> >
> >
> >
> > --
> > *Ishan Chhabra *| Rocket Scientist | RocketFuel Inc.
> >
>
>
>
> --
> *Ishan Chhabra *| Rocket Scientist | RocketFuel Inc.
>

--089e0115e7b439762104eab1f8b6--