Return-Path: 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 BD99410889 for ; Tue, 20 Aug 2013 16:29:44 +0000 (UTC) Received: (qmail 63913 invoked by uid 500); 20 Aug 2013 16:29:41 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 63861 invoked by uid 500); 20 Aug 2013 16:29:41 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 63852 invoked by uid 99); 20 Aug 2013 16:29:40 -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 16:29:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates 209.85.220.180 as permitted sender) Received: from [209.85.220.180] (HELO mail-vc0-f180.google.com) (209.85.220.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Aug 2013 16:29:36 +0000 Received: by mail-vc0-f180.google.com with SMTP id gf11so468670vcb.11 for ; Tue, 20 Aug 2013 09:29:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=ALGTnpx8OrYcGRcMABdyEHJD3qN0LoAZ6AFzAGszzSE=; b=uwds5F5oE8F2HDSJMpqLbehIbDMnVHn6WrJaEoHPqmFseSOPKpVY9Ox/X9ZelxsVVZ 7lo/CG5L+im/WH37gXoF5p+C181UGN6jvfkIipL0eEQFmTIRpieJQ9O6T9OegYShWkmQ teMLYKXLTlaUXrudq42Mm3YlenSSyKEsNo++lQp/9IWzX6bRW6wRvZ1yG0C6cYndZ823 rHnC0TCrwnR8LYVcqSJAx9+sZYWT1qWFPd7Q4yVuISbfra57TP7uf+8Wb2X0tK/8vLxj xfgKHX0a3n5TiMUFt3UNUKXAYgxqhZGRJIUctgQHw/8QvNvaoTLZ9W2oNGwdXdiLaulL FUXQ== MIME-Version: 1.0 X-Received: by 10.221.32.133 with SMTP id sk5mr1180702vcb.27.1377016155737; Tue, 20 Aug 2013 09:29:15 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.220.69.13 with HTTP; Tue, 20 Aug 2013 09:29:15 -0700 (PDT) In-Reply-To: References: Date: Tue, 20 Aug 2013 09:29:15 -0700 X-Google-Sender-Auth: TE6Tic_hJ_dUEZ80o7j88gS2IEg Message-ID: Subject: Re: Replication queue? From: Jean-Daniel Cryans To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a1133aa00d0167104e4638eff X-Virus-Checked: Checked by ClamAV on apache.org --001a1133aa00d0167104e4638eff Content-Type: text/plain; charset=ISO-8859-1 You can find a lot here: http://hbase.apache.org/replication.html And how many logs you can queue is how much disk space you have :) On Tue, Aug 20, 2013 at 7:23 AM, Jean-Marc Spaggiari < jean-marc@spaggiari.org> wrote: > 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 > --001a1133aa00d0167104e4638eff--