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 D07FCDE76 for ; Thu, 22 Nov 2012 02:10:50 +0000 (UTC) Received: (qmail 31951 invoked by uid 500); 22 Nov 2012 02:10:48 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 31753 invoked by uid 500); 22 Nov 2012 02:10:48 -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 31737 invoked by uid 99); 22 Nov 2012 02:10:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Nov 2012 02:10:48 +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 jiangbinglover@gmail.com designates 74.125.83.41 as permitted sender) Received: from [74.125.83.41] (HELO mail-ee0-f41.google.com) (74.125.83.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Nov 2012 02:10:36 +0000 Received: by mail-ee0-f41.google.com with SMTP id d41so5414406eek.14 for ; Wed, 21 Nov 2012 18:10:11 -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=RzAUA5Bb7WT5+zF3GcoMvwd3BeJAvDppG05hSAHdQQA=; b=VN+jfmBX8OaKheq1TZwsV9qWKR+XLaFBhuaKWsngdOAcLUPN/CQqH1i4ONhl9PdF5g vqVkXHpUdAUh6nFsaO3oG5PdBE+8paK8hsMvQK0ONLYyaBKrIAMWqhQNGzjYa0qgq+8Y OqIYzkOOKHQkPmjOh7PNmuBS2eH0Q+NvRfP72FH4ezUTEg+VrrTMtiV6QTEqnMo80PFK rspPHIRt5tZczSKuV0GxUyi4TrkM7jkGC9oZwgiotI0J8n7fK9WsnqEaWJpnB4vdv9iI ognjLLOXop+2JA9uQEiDl7hVxz0zIDLythsFzD5npSmc3K8HKjvd/pOPPHOcMQMK/Zvv npdw== MIME-Version: 1.0 Received: by 10.14.179.1 with SMTP id g1mr52143498eem.14.1353550211883; Wed, 21 Nov 2012 18:10:11 -0800 (PST) Received: by 10.14.224.134 with HTTP; Wed, 21 Nov 2012 18:10:11 -0800 (PST) In-Reply-To: <1353518865.44853.YahooMailNeo@web140604.mail.bf1.yahoo.com> References: <1353518865.44853.YahooMailNeo@web140604.mail.bf1.yahoo.com> Date: Thu, 22 Nov 2012 10:10:11 +0800 Message-ID: Subject: Re: delete rows without writing HLog may be appear in the future? From: Bing Jiang To: user@hbase.apache.org, lars hofhansl Content-Type: multipart/alternative; boundary=047d7b6244b890a41e04cf0bf7bf X-Virus-Checked: Checked by ClamAV on apache.org --047d7b6244b890a41e04cf0bf7bf Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable Thanks for all your suggestion and talk. One idea occurs to me why not check or restore wal when compaction executes. If it does, hbase can drop some unused hlog, I think that will be effective to the issue. please correct me if I am wrong. ---Bing 2012/11/22 lars hofhansl > I have it on my list of things to do to allow deferred WAL flush as a per > operation option (right now it's a CF option). > You really do not want to do anything with the WAL off. If you use > deferred flush there is still a chance that this might happen (the RS cou= ld > die in the few seconds after a Delete before it is flushed to the WAL), b= ut > it should be a rare occurrance. > > > -- Lars > > > > ________________________________ > From: Bing Jiang > To: user@hbase.apache.org > Sent: Wednesday, November 21, 2012 7:20 AM > Subject: Re: delete rows without writing HLog may be appear in the future= ? > > we need to confirm that put must be safe,but deletes must be quick and > low-latency. > On Nov 21, 2012 11:10 PM, "Michael Segel" > wrote: > > > Some time later? > > > > Time of course is relative, so I have to ask what occurred between the > > write and the delete? > > How much time? Did you have any compactions in between the write and th= e > > delete? > > > > Why are you not consistent in your use of the WAL ? > > > > > > On Nov 21, 2012, at 6:37 AM, Bing Jiang > wrote: > > > > > hi=A3=ACall. > > > I want to describe a phenomenon that happens to our hbase cluster. > > > I use puts(List) to insert many records with writing hlog enable= , > > > and some time later I delete all of these records with writing hlog > > disable. > > > When one week later, i scan the table, I found some records I have > delete > > > reappear again. > > > It is an interesting case. In my opinion, if we delete data without > > enable > > > writing hlog, when regionserver fails, the log will replay in another > > > regionserver. > > > Can anyone tell me if I persist on deleting records without enable > > writing > > > hlog, is there a way to prevent these records from reappearing again > some > > > time later? > > > > > > Cheers! > > > -- > > > Bing Jiang > > > weibo: http://weibo.com/jiangbinglover > > > BLOG: http://blog.sina.com.cn/jiangbinglover > > > BLOG: http://www.binospace.com > > > National Research Center for Intelligent Computing Systems > > > Institute of Computing technology > > > Graduate University of Chinese Academy of Science > > > > > --=20 Bing Jiang Tel=A3=BA(86)134-2619-1361 weibo: http://weibo.com/jiangbinglover BLOG: http://blog.sina.com.cn/jiangbinglover National Research Center for Intelligent Computing Systems Institute of Computing technology Graduate University of Chinese Academy of Science --047d7b6244b890a41e04cf0bf7bf--