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 C78F910F77 for ; Tue, 25 Nov 2014 04:33:11 +0000 (UTC) Received: (qmail 83788 invoked by uid 500); 25 Nov 2014 04:33:10 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 83698 invoked by uid 500); 25 Nov 2014 04:33:10 -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 83686 invoked by uid 99); 25 Nov 2014 04:33:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Nov 2014 04:33:09 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lhofhansl@yahoo.com designates 216.109.114.254 as permitted sender) Received: from [216.109.114.254] (HELO nm44-vm3.bullet.mail.bf1.yahoo.com) (216.109.114.254) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Nov 2014 04:33:04 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.com; b=GY2Aa6JwkzZ/sAT0LkcSmuNN8DlAvFf0DNCwrtyPwouIetZnRRIppk+y5pfGc1MSZzi1VJsL2SMHw0BZtC7KspCCkNwqEwxN8+KyXrC+l5y0/CMlWLzha92HE0HIfriv+nnvjvtRcG817M5IjC/ZnMyZrwgGoFmUPSRCFxAt88/ZFZ/GWHaBuNp80TL26ZUHOzmFKIKlIN5/FX+HkVB6h3l8/oVjkiFauYTtn30UfeGGn2PQkOAj82GCCm3DfB1j3NVoPDtl9WcrVaXSZasiez64iuKZaWz0t2Kw0yD8bTAhMkjki2Ct0mdkNA35gVA8QVgiNIxWf+XRNv7gFS/aZQ==; Received: from [98.139.214.32] by nm44.bullet.mail.bf1.yahoo.com with NNFMP; 25 Nov 2014 04:29:34 -0000 Received: from [98.139.212.240] by tm15.bullet.mail.bf1.yahoo.com with NNFMP; 25 Nov 2014 04:29:34 -0000 Received: from [127.0.0.1] by omp1049.mail.bf1.yahoo.com with NNFMP; 25 Nov 2014 04:29:34 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 358704.25349.bm@omp1049.mail.bf1.yahoo.com X-YMail-OSG: Um6wGFoVM1mKotzIGvVGrSN0eCtnKGVnKNMHqavRX.Dun3Q.TKACsCMnYgR_bAm d4g7bCEdMAj3b5KFx.LjMA0iBT2HidjfEcizRDRFpe7vTHULZvRXM3EYsb_cLujMSJ46ecn41r7f bIbdPFLWomZpru.iW.KWN5y.kbXGxqfUNV.DEHoBQ2LbfSNnbRIxGlqfKT_i8cUBIrqtwHWIwyjf 5vh.hu2zQ81.26dZddksQXwev_2G_CekDQ9W0dhikdjxlwmKHnOuArLgJ2NORhPgo52Tse9HyzCT .MakPjYMArgJVSTQZ5bN.xQdZbLXN6GnAeTxkYVEmF3LQU.Qf3.WeT3NZ.6ay6eDmSnTaIeiVB2c qs6.jfsw.Qww3zbzJgs.0jLFGe86Q06GJ3FsQlJxpGoTn2eSpqUR1OaKc0ErfbT1GN9RqhhxqsYn _er9HAY9DwJ8QqxKC1ty9oCCPuucyCFr5t9yUwyyyIOGy0yeJO_M88CUFFkzbKHzrSuys Received: by 66.196.80.125; Tue, 25 Nov 2014 04:29:33 +0000 Date: Tue, 25 Nov 2014 04:29:33 +0000 (UTC) From: lars hofhansl Reply-To: lars hofhansl To: "dev@hbase.apache.org" Message-ID: <1085768760.555014.1416889773300.JavaMail.yahoo@jws10648.mail.bf1.yahoo.com> In-Reply-To: References: Subject: Re: Replication terminology "master-master" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_555013_775437050.1416889773295" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_555013_775437050.1416889773295 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hmm... From that angle all we really have is master-slave replication, with= out limit as how it can be setup.A master can be slave too, and a slave a m= aster, and cycles are allowed. I find "cyclical replication" more confusing than "master-master" (although= it's true that master-master is strictly a subset of cyclical - just a cyc= le of two). We might want to scrap all the terms and just state (hopefully a bit nicer)= what I tried to say in the first two sentences above. -- Lars From: Misty Stanley-Jones To: dev@hbase.apache.org=20 Sent: Monday, November 24, 2014 7:26 PM Subject: Replication terminology "master-master" =20 Hi all, I think "master-master" is a term that should be re-thought. It is not really a "type" of replication, but refers to a characteristic of=C2=A0 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 changing our terminology? Thanks, Misty ------=_Part_555013_775437050.1416889773295--