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 226DA10FFE for ; Mon, 28 Jul 2014 10:17:43 +0000 (UTC) Received: (qmail 38352 invoked by uid 500); 28 Jul 2014 10:17:41 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 38289 invoked by uid 500); 28 Jul 2014 10:17:41 -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 38241 invoked by uid 99); 28 Jul 2014 10:17:40 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jul 2014 10:17:40 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tianq01@gmail.com designates 209.85.216.49 as permitted sender) Received: from [209.85.216.49] (HELO mail-qa0-f49.google.com) (209.85.216.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jul 2014 10:17:22 +0000 Received: by mail-qa0-f49.google.com with SMTP id dc16so7634520qab.36 for ; Mon, 28 Jul 2014 03:16:57 -0700 (PDT) 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=LQrQl3nAGwRI0K/ACMu2SPGAeTclx7WHK5Nt/KPlhNI=; b=z9amUaAp8xlMYzgi6eKru6cKa7zY8GPhxQBZ4clcgTw3GcmMbWn4yQ2B10S4teDj3O iaGsiFewYBAz+5DlULQKuIoBqV1XSSsfJPg75l4Tj6eOonydr3NMdMIwyPKtOhImlT4T PwmVjrzb1e7iaE3ufAEPmxZeH8VlUK0xcQp37N4zuowhZ2cb+ijNO6yLbr4AI1sPI52C FP7Yb73NE2w9BWO5BMIOL3iNqS7iNyS9q848Vz1pku4KjP7M4xIJu3dX54OHDiKOUfYL xo/DzrNrcK1DLIclht1hWK780CTCZRcjdhhKi61kcK1gZ0UUmUX/9gIEv248QbiZf7WI a37g== MIME-Version: 1.0 X-Received: by 10.140.105.72 with SMTP id b66mr56720567qgf.30.1406542617364; Mon, 28 Jul 2014 03:16:57 -0700 (PDT) Received: by 10.140.43.228 with HTTP; Mon, 28 Jul 2014 03:16:57 -0700 (PDT) In-Reply-To: <2FB48A2A-403A-470B-919C-F8620ABCD456@gmail.com> References: <2FB48A2A-403A-470B-919C-F8620ABCD456@gmail.com> Date: Mon, 28 Jul 2014 18:16:57 +0800 Message-ID: Subject: Re: delete a row in hbase:meta From: Qiang Tian To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a1137d35811d06d04ff3e3960 X-Virus-Checked: Checked by ClamAV on apache.org --001a1137d35811d06d04ff3e3960 Content-Type: text/plain; charset=UTF-8 unfortunately the log was deleted and cannot be reproduced...only have below data in meta table just before the problem happened : moma,,1406539662740.c0a589ce74c8bad980d16947fdf56 column=info:regioninfo, timestamp=1406541888175, value={ENCODED => c0a589ce74c8bad980d16947fdf56036, NAME => 'moma,,1406539662740.c0a589ce74c8bad9 036. 80d16947fdf56036.', STARTKEY => '', ENDKEY => ''} moma,,1406539662740.c0a589ce74c8bad980d16947fdf56 column=info:seqnumDuringOpen, timestamp=1406541888222, value=\x00\x00\x00\x00\x00\x00\x00*\x01* 036. moma,,1406539662740.c0a589ce74c8bad980d16947fdf56 column=info:server, timestamp=1406541888222, value=HRegionServer3:60020 036. moma,,1406539662740.c0a589ce74c8bad980d16947fdf56 column=info:serverstartcode, timestamp=1406541888222, value=1406312768813 036. moma,\x00"\x00\x00\x00\x012+\xF8\xCB\xF0,14064686 column=info:seqnumDuringOpen, timestamp=1406478771359, value=\x00\x00\x00\x00\x00\x00\x00*\x01* 25503.6936ebd2ae1d85fc09f243a767229339. moma,\x00"\x00\x00\x00\x012+\xF8\xCB\xF0,14064686 column=info:server, timestamp=1406478771359, value=HRegionServer2:60020 25503.6936ebd2ae1d85fc09f243a767229339. moma,\x00"\x00\x00\x00\x012+\xF8\xCB\xF0,14064686 column=info:serverstartcode, timestamp=1406478771359, value=1406312832708 25503.6936ebd2ae1d85fc09f243a767229339. there are 2 rowkeys: moma,,1406539662740.c0a589ce74c8bad980d16947fdf56036. moma,\x00"\x00\x00\x00\x012+\xF8\xCB\xF0,1406468625503.6936ebd2ae1d85fc09f243a767229339. the first was deleted via drop 'moma' command, the second cannot. it looks during delete table, we look up "info:regioninfo" in meta to locate the related regions, since the second has no "info:regioninfo" column, it is ignored by hbase? further investigation shows the 2 regions are just after split(info:seqnumDuringOpen=1), but it looks updating meta during split should have updated those info... thanks. On Mon, Jul 28, 2014 at 1:28 PM, Ted Yu wrote: > Using hbck is recommended for such scenario. > > Did you look at master / region server logs to see if there is some clue > during table drop operation ? > > Cheers > > On Jul 27, 2014, at 10:00 PM, Qiang Tian wrote: > > > Thanks Ted, > > An user on 0.96 deletes a table region on HDFS by mistake, so he wants to > > delete the entire table and recreate it. after disable&drop, he finds the > > table's region info still exists in meta table.. > > > > from the code, we should be able to delete the related info during table > > drop, I suspect the startRow(,,) in getTableStartRowForMeta > > might not be correct? > > > > ps could hbck tool could fix it? (he deleted it finally via java code, > will > > see if we could repro it...) > > > > > > > > On Mon, Jul 28, 2014 at 12:05 PM, Ted Yu wrote: > > > >> Deleting from hbase:meta is for advanced users :-) > >> > >> Can you tell us why that row needs to be deleted ? > >> > >> Cheers > >> > >> > >> On Sun, Jul 27, 2014 at 8:32 PM, Qiang Tian wrote: > >> > >>> Hi Guys, > >>> > >>> for a row in hbase:meta like below, how to delete it? due to the chars > of > >>> startkey, it cannot be found. > >>> delete > >> > 'hbase:meta','moma,\x00"\x00\x00\x00\x012+\xF8\xCB\xF0,1406468625503.6936ebd2ae1d85fc09f243a767229339.','info:seqnumDuringOpen' > >>> > >>> ERROR: Row Not Found > >>> > >>> thanks! > >> > --001a1137d35811d06d04ff3e3960--