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 D56A8EAC3 for ; Mon, 25 Feb 2013 15:03:40 +0000 (UTC) Received: (qmail 18517 invoked by uid 500); 25 Feb 2013 15:03:38 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 18456 invoked by uid 500); 25 Feb 2013 15:03:38 -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 18437 invoked by uid 99); 25 Feb 2013 15:03:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Feb 2013 15:03:37 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.82.54] (HELO mail-wg0-f54.google.com) (74.125.82.54) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Feb 2013 15:03:31 +0000 Received: by mail-wg0-f54.google.com with SMTP id fm10so2441103wgb.21 for ; Mon, 25 Feb 2013 07:03:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=1CQP3+XDQABWW5jJKgaLSl7KDo8mw7GIymudZNQIB+k=; b=W1XSvj9ZvHVTfEMDVtaAHx67zS0vlUBM9IyrFtcDY7nFetpjyzUw0zK37/xEmZ6k5Y 5Ilul188FvUPAKyOr1UpfzjyHPukTpAkDwab0Dm5460th0XjnVt5KrOI1IJGr0A/h1Xw kzZZAdfGK/vlcEwwgFmYeiOrOsnlQmzc8kMe8GFRRA+5RPkwoDArM4Y2OohrsAXuldKd ndYooLfmSD2jOlGMFBbvy5JM583KPHrUFkZYAG/0xiKutM7A2xfxgJv7Y1r+jdJ3W6k7 KHHuj1eD36qAodpE8MmGgjovp4YJ4wvLbWH1cWMu6Z2Jnfqj4kHDNUXwtmF+IUR5yQhr HXVQ== X-Received: by 10.180.78.35 with SMTP id y3mr12892249wiw.22.1361804587057; Mon, 25 Feb 2013 07:03:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.176.71 with HTTP; Mon, 25 Feb 2013 07:02:46 -0800 (PST) In-Reply-To: References: From: Jean-Marc Spaggiari Date: Mon, 25 Feb 2013 10:02:46 -0500 Message-ID: Subject: Re: CatalogJanitor: REGIONINFO_QUALIFIER is empty To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=f46d043c7b84aa44a704d68dd636 X-Gm-Message-State: ALoCoQnitk+t0PRqakqEhr37yFAxb8srDgNRdNlYDs7ZEJnqbCmA7Fjb/tKv1nG7tifPy4ER5nlT X-Virus-Checked: Checked by ClamAV on apache.org --f46d043c7b84aa44a704d68dd636 Content-Type: text/plain; charset=UTF-8 Ok. Document a JIRA and take a look at hbck to add that. JM 2013/2/25 Ted Yu > I think hbck should be enhanced to deal with this situation. > > On Mon, Feb 25, 2013 at 6:56 AM, Jean-Marc Spaggiari < > jean-marc@spaggiari.org> wrote: > > > Hi Dave, > > > > Thanks for the details. > > > > Is it something that we should think about adding into HBCK? > > > > Seems that it can detect them "Number of empty REGIONINFO_QUALIFIER rows > in > > .META.: 6" but it's not fixing them nor listing them. > > > > JM > > > > 2013/2/25 ramkrishna vasudevan > > > > > Thanks for the info Dave. Others will be benefited too. > > > > > > Regards > > > Ram > > > > > > On Mon, Feb 25, 2013 at 7:25 PM, Dave Latham > > wrote: > > > > > > > We recently saw some of these warnings in a cluster we were setting > up. > > > > These warnings mean there are rows in the META table that are missing > > one > > > > of the expected columns. In our case, we verified that these regions > > > > didn't appear to exist in HDFS either and the table itself showed no > > > holes > > > > or problems in hbck or via our application. After looking at the > > > > timestamps of the other data in these rows in META we determined that > > the > > > > remaining columns in META had been written on an earlier incarnation > > of a > > > > table with the same name. I.e. we created a table once, put data in > > it, > > > > deleted the table, created a new table of the same name, and > apparently > > > not > > > > everything was correctly deleted from META. I'm not sure how that > > > > happened, but to clean it up we manually removed those rows from META > > and > > > > didn't observe any more WARNings or problems afterward. There's > > another > > > > mailing list thread from some months back from someone with a similar > > > issue > > > > and resolution. Good luck! > > > > > > > > Dave > > > > > > > > > > > > On Sun, Feb 24, 2013 at 5:03 PM, Jean-Marc Spaggiari < > > > > jean-marc@spaggiari.org> wrote: > > > > > > > > > Hi, > > > > > > > > > > I'm wondering, how much should we worrie about those warnings: > > > > > WARN org.apache.hadoop.hbase.master.CatalogJanitor: > > > REGIONINFO_QUALIFIER > > > > is > > > > > empty in keyvalues={ > > > > > > > > > > I have 6 of them show each time the CatalgoJanitor is running (5 > > > > minutes). > > > > > > > > > > Doesn't seems to really be an issue, but then why is it a WARN? > > > > > > > > > > Thanks, > > > > > > > > > > JM > > > > > > > > > > > > > > > --f46d043c7b84aa44a704d68dd636--