Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D5883C59C for ; Thu, 19 Jul 2012 17:50:56 +0000 (UTC) Received: (qmail 54197 invoked by uid 500); 19 Jul 2012 17:50:56 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 54155 invoked by uid 500); 19 Jul 2012 17:50:56 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 54147 invoked by uid 99); 19 Jul 2012 17:50:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jul 2012 17:50:56 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jdcryans@gmail.com designates 209.85.217.169 as permitted sender) Received: from [209.85.217.169] (HELO mail-lb0-f169.google.com) (209.85.217.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jul 2012 17:50:49 +0000 Received: by lbjn8 with SMTP id n8so5103882lbj.14 for ; Thu, 19 Jul 2012 10:50:29 -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 :x-google-sender-auth:message-id:subject:from:to:content-type; bh=LHlJeNMjhRS08gjFq0ef4FtesR66a6+UNJQ4hPVc5Vs=; b=xSeIvcCOOC2tbao4nhy1qYMrJ2Y2PI9RtFQFLb97hNa5xjrc3EK9QSu88zWSVWKX6z 9+L6kRs6ANKTLGxrpXkN+7yjjPyz9fnSM0NY0c3UpBb0LbYTaAUr+T7CxPnGhj3bYqmv 5AnGUxzPvPw/rAqPSPRG9EY3ZtrE6fyIr5gJ047Z4wrqAB6KbT6gU8Rcx+GzooNcvXnB scRivimnyhFplyI8j4j1/huON6LqoD2N4ZGvC+PRSGj+574bj0M35dsY334hxFAFGpcX 8ar/uNkmQs9Do3SrveXlN6oHJUPrPp3tVNrNW2jAcizTulaAXSK7f7mig/EIGTZuH0KM npIw== MIME-Version: 1.0 Received: by 10.152.104.44 with SMTP id gb12mr3127597lab.29.1342720229420; Thu, 19 Jul 2012 10:50:29 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.114.23.201 with HTTP; Thu, 19 Jul 2012 10:50:29 -0700 (PDT) In-Reply-To: <5007942b.6988440a.4198.4e51SMTPIN_ADDED@mx.google.com> References: <5007942b.6988440a.4198.4e51SMTPIN_ADDED@mx.google.com> Date: Thu, 19 Jul 2012 10:50:29 -0700 X-Google-Sender-Auth: Tp9Tg063XdLSN3hhKQHo77wSQY8 Message-ID: Subject: Re: Wondering what hbck should do in this situation From: Jean-Daniel Cryans To: dev@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jul 18, 2012 at 9:56 PM, Ramkrishna.S.Vasudevan wrote: > J-d > Corrections, if META does not have an entry then we cannot know if it is > splitted or not.. Apologies for that. > > I think we need to check for Reference files and if the opening fails we > need to report it. That should be the way. > But we should also confirm whether this region was split properly, right? That's what I'm wondering about. It seems to me that hbck currently is overly aggressive fixing things (see also HBASE-6417 where it merged .META.). So should we have all the heuristics to detect problems and then add the corner cases after as people find them? Or should we let the users decide what should be fixed? It could be that we should ask more questions to the users. I'm thinking out loud here. J-D