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 9767DDC15 for ; Mon, 20 May 2013 07:35:58 +0000 (UTC) Received: (qmail 7492 invoked by uid 500); 20 May 2013 07:35:56 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 6026 invoked by uid 500); 20 May 2013 07:35:50 -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 5414 invoked by uid 99); 20 May 2013 07:35:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 May 2013 07:35:49 +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 (nike.apache.org: domain of varun@pinterest.com designates 209.85.210.179 as permitted sender) Received: from [209.85.210.179] (HELO mail-ia0-f179.google.com) (209.85.210.179) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 May 2013 07:35:43 +0000 Received: by mail-ia0-f179.google.com with SMTP id i20so6135766ian.10 for ; Mon, 20 May 2013 00:35:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=1IId+9GzQNpa6kDC/tAydwrOPoTQxAajUlGOFG7zz60=; b=YfQ+EDVLFgdpYT/6hM/zbXkjyjHJkzusFZj951Bn8Ebx8OnN5PuthAkE9clC4S/lhj jjud+d8ZD4frGSz+6levELDJ7wYyFa0B9P85AN3rHeDIOeSkX9IfaUhQp+VrwRI483+Q d2S6JYIhMdqs202iBrKjjv3iQKKTeTbEq7Ku0P8+ePR679Z96iZtWOuyiEHaRuQOj+a4 uAGe6krqjzbHygOFA/KCZqVAxC7p291DW+b9FtBXIUAx2y0NIacewth3AkdyV0HlFcxK 2+d72tnoAEEk7ZtzUWZGiY9ow4jw7t62j1agilZhZR6gzJw9ywc6LE3wXuNuQZAEpYIg CM5g== MIME-Version: 1.0 X-Received: by 10.50.62.13 with SMTP id u13mr3320239igr.19.1369035321864; Mon, 20 May 2013 00:35:21 -0700 (PDT) Received: by 10.231.84.6 with HTTP; Mon, 20 May 2013 00:35:21 -0700 (PDT) In-Reply-To: <1369021773.11235.YahooMailNeo@web140605.mail.bf1.yahoo.com> References: <1369021773.11235.YahooMailNeo@web140605.mail.bf1.yahoo.com> Date: Mon, 20 May 2013 00:35:21 -0700 Message-ID: Subject: Re: Questions about HBase replication From: Varun Sharma To: user@hbase.apache.org, lars hofhansl Content-Type: multipart/alternative; boundary=047d7bdc07a80b86e404dd216065 X-Gm-Message-State: ALoCoQnIpnhMZGv3s6c4afuMsp/VtwzQ+zl5JC6G2fATbjxQIYho+gjJxtV0FUjzIPE8lGyXRsEy X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdc07a80b86e404dd216065 Content-Type: text/plain; charset=ISO-8859-1 Hi Lars, Thanks for the response. Regarding #2 again, so if RS1 failed, then the following happens... 1) RS2 takes over its logs... 2) Master renames the log containing directory to have a -splitting in the path 3) Does RS2 already know about the "-splitting" path ? Also on a related note, was there a reason that we have all region servers watching all other region server's queue of logs. Otherwise, couldn't the master have done the reassignment of outstanding logs to other region servers more fairly upon failure ? Thanks Varun On Sun, May 19, 2013 at 8:49 PM, lars hofhansl wrote: > #1 yes > #2 no > > :) > > Now, there are scenarios where inconsistencies can happen. The edits are > not necessarily shipped in order when there are failures. > So it is possible to have some Puts at T1 and some Deletes at T2 (T1 < > T2), and end up with the deletes shipped first. > Now imagine a compaction happens at the slave after the Deletes are > shipped to the slave, but before the Puts are shipped... The Puts will > reappear. > > -- Lars > > > > ________________________________ > From: Varun Sharma > To: user@hbase.apache.org > Sent: Sunday, May 19, 2013 12:13 PM > Subject: Questions about HBase replication > > > Hi, > > I have a couple of questions about HBase replication... > > 1) When we ship edits to slave cluster - do we retain the timestamps in the > edits - if we don't, I can imagine hitting some inconsistencies ? > > 2) When a region server fails, the master renames the directory containing > WAL(s). Does this impact reading of those logs for replication ? > > Thanks > Varun > --047d7bdc07a80b86e404dd216065--