Return-Path: 
 <user-return-38273-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-user-archive@www.apache.org
Delivered-To: apmail-hbase-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6D5B0104BB
	for <apmail-hbase-user-archive@www.apache.org>;
 Tue, 20 Aug 2013 14:24:19 +0000 (UTC)
Received: (qmail 76881 invoked by uid 500); 20 Aug 2013 14:24:08 -0000
Delivered-To: apmail-hbase-user-archive@hbase.apache.org
Received: (qmail 76486 invoked by uid 500); 20 Aug 2013 14:24:08 -0000
Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hbase.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hbase.apache.org>
List-Post: <mailto:user@hbase.apache.org>
List-Id: <user.hbase.apache.org>
Reply-To: user@hbase.apache.org
Delivered-To: mailing list user@hbase.apache.org
Received: (qmail 76347 invoked by uid 99); 20 Aug 2013 14:24:07 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Aug 2013 14:24:07 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW
X-Spam-Check-By: apache.org
Received-SPF: error (athena.apache.org: local policy)
Received: from [209.85.220.178] (HELO mail-vc0-f178.google.com)
 (209.85.220.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Aug 2013 14:24:02 +0000
Received: by mail-vc0-f178.google.com with SMTP id ha12so333934vcb.9
        for <user@hbase.apache.org>; Tue, 20 Aug 2013 07:23:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=x-gm-message-state:mime-version:from:date:message-id:subject:to
         :content-type;
        bh=p+H2VDHIOW4xq9OMy1xkbMzyST/fqUjqPfVW8SeLy/w=;
        b=Oq3OU3HLj5HEoGRjK2bgEdUVZO/0y99x3BKUZ1qZYsW15v0XIJjnMjjhZjfHtU0Lfx
         XqumB12Y+AwxRPrLoma4wAFdLd3K5hPO3BwfApASvrls8u3BkK+eJdCMVmp7Z0g80Mtj
         BYf0zubpr3vMQlkAJ6nReHYWcaNi5PuwTxRawLCz3E92bh610+KTCjhC2vmHQKBGxULo
         QDrOMIdU1UOPotHsAtQdrB95EgVeoZpuzcBtWFzU5jNLyxrg7en4BIuVoR8oRUtIqJBm
         UBx3Eemp5rZKnmGPwLccpMoajkyyy7eVJjXJsjoWZ1dAhRaOtX8Z8HXJDKO8kkRJPI4T
         XN2w==
X-Gm-Message-State: 
 ALoCoQmd5uVuw3Iqj+zrQj+STskCBhV82xQ9sLetG43aGMXAWqmgBCtPNEg5vDky4uf+SStLRVGM
X-Received: by 10.58.119.233 with SMTP id kx9mr1497683veb.3.1377008601423;
 Tue, 20 Aug 2013 07:23:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.35.82 with HTTP; Tue, 20 Aug 2013 07:23:01 -0700 (PDT)
From: Jean-Marc Spaggiari <jean-marc@spaggiari.org>
Date: Tue, 20 Aug 2013 10:23:01 -0400
Message-ID: 
 <CAPQV63XJJMtLBTRVwb-RBYh7xuK=SY7Hv4xf8fuzcG2zvS6bdw@mail.gmail.com>
Subject: Replication queue?
To: user <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a11c391be8a746404e461cce7
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c391be8a746404e461cce7
Content-Type: text/plain; charset=UTF-8

Hi,

If I have a master -> slave replication, and master went down, replication
will start back where it was when master will come back online. Fine.
If I have a master -> slave replication, and slave went down, is the data
queued until the slave come back online and then sent? If so, how big can
be this queu, and how long can the slave be down?

Same questions for master <-> master... I guess for this one, it's like for
the 1 line above and it's fine, right?

Thanks,

JM

--001a11c391be8a746404e461cce7--