Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D3023C4FE for ; Wed, 10 Dec 2014 10:03:14 +0000 (UTC) Received: (qmail 87433 invoked by uid 500); 10 Dec 2014 10:03:13 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 87361 invoked by uid 500); 10 Dec 2014 10:03:13 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 87348 invoked by uid 99); 10 Dec 2014 10:03:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2014 10:03:12 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lars.george@gmail.com designates 209.85.192.43 as permitted sender) Received: from [209.85.192.43] (HELO mail-qg0-f43.google.com) (209.85.192.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2014 10:03:07 +0000 Received: by mail-qg0-f43.google.com with SMTP id i50so1849752qgf.30 for ; Wed, 10 Dec 2014 02:02:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HwBtzIF62UGqBA6Vt+Q+OXQoKl2inCtNEaGIP7PimI4=; b=AoQuSehvza9QpJb/3OTwhv5tI4nelsXSMzBqX0jp9+dNtg2FGscnB7IJYAzhZNXybd R9LYiBn2CefWL7fzmmuyd/3sZKksPQ80MiaDQ+6X5nz1stSsnFZkoMN0EjPCfIkXjzOq VBBB3zy+r+t4IPbkItEp2TKutiEzH1mTBPtypRrQ/RNIckKN+dygvxbEtuaT8/KprEoi PxMv3V7VR3Y/QrTzmF3e3p+YuPpgfA0GEVbVK0U7g5+DlhLTFjxmn0a+8R6E8vQgejY6 bvUFl13Ngqc1oC7/3pQHb0nOtBBDsYuj8/hWFovWToC5n35bwVdvg3i1g7BNs/35xU4w mfFw== MIME-Version: 1.0 X-Received: by 10.140.37.71 with SMTP id q65mr6232312qgq.42.1418205767089; Wed, 10 Dec 2014 02:02:47 -0800 (PST) Received: by 10.229.134.76 with HTTP; Wed, 10 Dec 2014 02:02:46 -0800 (PST) In-Reply-To: References: Date: Wed, 10 Dec 2014 11:02:46 +0100 Message-ID: Subject: Re: Replication terminology "master-master" From: Lars George To: "dev@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a11c13d36f7467f0509d9c282 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c13d36f7467f0509d9c282 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable +1 :) On Wed, Dec 10, 2014 at 5:36 AM, Nick Dimiduk wrote: > I suggest we drop the lingo and just say what we mean explicitly: "A > cluster may act as both a replication source and destination > simultaneously." > > On Tuesday, December 9, 2014, Misty Stanley-Jones < > mstanleyjones@cloudera.com> wrote: > > > Can I get some consensus on what we should be saying about different > > replication types? It's a bit over my head and I don't feel comfortable > > making a unilateral decision. > > > > On Sun, Nov 30, 2014 at 8:40 AM, Michael Segel < > michael_segel@hotmail.com > > > > > wrote: > > > > > Both clusters are alive, but the terms active/passive means who=E2=80= =99s > serving > > > the data. > > > > > > Your =E2=80=98master=E2=80=99 is the HBase cluster which is r/w and s= erving data. > > > > > > Your =E2=80=98slave=E2=80=99 is the cluster that is passive or only s= erving read only > > data. > > > > > > To your point that active/passive may be incorrect because you can re= ad > > > from the passive, too. > > > > > > Peer to Peer may be incorrect in that while both are peers, you=E2=80= =99re > > > actively writing to one, while the other gets a copy of the data and = is > > > passive. > > > Understanding that in context a HBase cluster can be active for one > data > > > set and passive for another. > > > > > > Active/Active would be that I could write to either and there would b= e > > > some form of eventual consistency. > > > > > > On Nov 28, 2014, at 1:15 AM, Misty Stanley-Jones < > > > mstanleyjones@cloudera.com > wrote: > > > > > > > I don't think active/passive is what we mean here, since both > clusters > > > are > > > > fully "active" from the perspective of clients, right? The slave > > cluster > > > is > > > > not actually read-only, is it? > > > > > > > > On Thu, Nov 27, 2014 at 10:50 PM, Michael Segel < > > > michael_segel@hotmail.com > > > > > wrote: > > > > > > > >> master - master? > > > >> > > > >> Do you mean active - active ? > > > >> > > > >> replace master and slave with active and passive. > > > >> > > > >> > > > >> On Nov 25, 2014, at 3:26 AM, Misty Stanley-Jones < > > > >> mstanleyjones@cloudera.com > wrote: > > > >> > > > >>> Hi all, > > > >>> > > > >>> I think "master-master" is a term that should be re-thought. It i= s > > not > > > >>> really a "type" of replication, but refers to a characteristic of > a > > > >>> cluster, specifically a cluster which participates in multiple > > clusters > > > >>> with different roles -- it is a slave in one cluster and a master > in > > > >>> another cluster. I think with the current terminology, people > confuse > > > it > > > >>> with "cyclical" replication, in which two clusters replicate to > each > > > >> other, > > > >>> and eventually each has all the data from both. > > > >>> > > > >>> Since master-master in this sense is really not a type of > > replication, > > > I > > > >>> think we should just scrap it. You can have master-slave > replication > > or > > > >>> cyclical replication, or a combination. With master-slave > > replication, > > > a > > > >>> cluster can fulfill both roles at the same time, as long as it is > in > > > >>> different clusters. This is easy to understand as a sort of > recursive > > > >>> cascade. > > > >>> > > > >>> Am I explaining it right, and what do you guys think about changi= ng > > our > > > >>> terminology? > > > >>> > > > >>> Thanks, > > > >>> Misty > > > >> > > > >> > > > > > > > > > --001a11c13d36f7467f0509d9c282--