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 4BFA210773 for ; Tue, 25 Feb 2014 18:12:20 +0000 (UTC) Received: (qmail 64203 invoked by uid 500); 25 Feb 2014 18:12:17 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 64115 invoked by uid 500); 25 Feb 2014 18:12:16 -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 64107 invoked by uid 99); 25 Feb 2014 18:12:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Feb 2014 18:12:16 +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 yuzhihong@gmail.com designates 209.85.213.41 as permitted sender) Received: from [209.85.213.41] (HELO mail-yh0-f41.google.com) (209.85.213.41) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Feb 2014 18:12:10 +0000 Received: by mail-yh0-f41.google.com with SMTP id f73so7442814yha.0 for ; Tue, 25 Feb 2014 10:11:49 -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=R4/dUUet0n/veuCKXpD6F1+BJ6JjyzrMnpy7yBcigYI=; b=FekkpA7wElpwK57sFASw3wUNYsyySyDWQXeF3OkunwQKIIT4cP8khfw+gPMAIRBU02 eAsNCnTyEMABM6g2juCKj2fIDJ06SnOcOcVr6TclM/dAgQoQxCqNB/dohywxmH0QI1pQ OcGneil4DgFB8m77dAhUptjyig5KTPDi5Or9rO6S8Q8O5BdBPN+nOxxDGVY98hq7oRDi qlW8CTRfvZhp+Kcpgnj9K4cnKtuaiLRBkeyM+bwaFSV5WY58tErR1m5EZ/IjYJBJ61He PDzxV3SpZgpOhsW6SjoshB8bpsLl0btvoHj4IuYgFPouUx3z1mGu6qAF0P3m3tlbLG7a vOew== MIME-Version: 1.0 X-Received: by 10.236.152.36 with SMTP id c24mr1706997yhk.118.1393351909620; Tue, 25 Feb 2014 10:11:49 -0800 (PST) Received: by 10.170.79.86 with HTTP; Tue, 25 Feb 2014 10:11:49 -0800 (PST) In-Reply-To: <1393351519.99827.YahooMailNeo@web190106.mail.sg3.yahoo.com> References: <1393351519.99827.YahooMailNeo@web190106.mail.sg3.yahoo.com> Date: Tue, 25 Feb 2014 10:11:49 -0800 Message-ID: Subject: Re: Need some information over WAL From: Ted Yu To: "user@hbase.apache.org" , Dhaval Shah Content-Type: multipart/alternative; boundary=20cf3040e96e9ec2f804f33f05cb X-Virus-Checked: Checked by ClamAV on apache.org --20cf3040e96e9ec2f804f33f05cb Content-Type: text/plain; charset=ISO-8859-1 bq. Hbase uses append operation in hdfs to store/log WAL. Following append operation, hdfs sync operation would be called for persistence. FYI On Tue, Feb 25, 2014 at 10:05 AM, Dhaval Shah wrote: > Inline > > Regards, > Dhaval > > > ________________________________ > From: Upendra Yadav > To: user@hbase.apache.org > Sent: Tuesday, 25 February 2014 1:00 PM > Subject: Need some information over WAL > > > I have also doubt over WAL(write ahead log). > > In hdfs we can write a new file or we can append to old file. > > Is that correct : > 1. WAL only logs operations not its data... just like disk journaling(ext4) > - No WAL is a log of all new data, not just the operations > > 2. In case of Region Server failure... WAL replay will depends on Client to > get each operation's data that yet not committed/flushed to hdfs. > - No client will not generally know of a region server failure. It gets > the data from the WAL and replays it. The client may not even exist when a > region server crashes > > 3. Hbase uses append operation in hdfs to store/log WAL. > - Yes > > Thanks... --20cf3040e96e9ec2f804f33f05cb--