Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A7591200C80 for ; Wed, 10 May 2017 18:41:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A5FE2160B9C; Wed, 10 May 2017 16:41:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 00A63160BB4 for ; Wed, 10 May 2017 18:41:08 +0200 (CEST) Received: (qmail 45893 invoked by uid 500); 10 May 2017 16:41:08 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 45881 invoked by uid 99); 10 May 2017 16:41:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 May 2017 16:41:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id B48001813ED for ; Wed, 10 May 2017 16:41:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id EGPkI-yRQYL2 for ; Wed, 10 May 2017 16:41:07 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id DB3B65FDC2 for ; Wed, 10 May 2017 16:41:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 34D4BE0940 for ; Wed, 10 May 2017 16:41:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 6307C21E16 for ; Wed, 10 May 2017 16:41:04 +0000 (UTC) Date: Wed, 10 May 2017 16:41:04 +0000 (UTC) From: "Xiang Li (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-18022) Refine the error message issued with TableNotFoundException when expected table is not the same as the one fetched from meta MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 10 May 2017 16:41:09 -0000 [ https://issues.apache.org/jira/browse/HBASE-18022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004987#comment-16004987 ] Xiang Li commented on HBASE-18022: ---------------------------------- Refine the error message as bq. Region of 't1,,1492763727308.a9146e6548fc2eeaca2b2d718db32230.' is expected in the tabe of 't1', but hbase:meta says it is in the table of 't2'. hbase:meta might be damaged. > Refine the error message issued with TableNotFoundException when expected table is not the same as the one fetched from meta > ---------------------------------------------------------------------------------------------------------------------------- > > Key: HBASE-18022 > URL: https://issues.apache.org/jira/browse/HBASE-18022 > Project: HBase > Issue Type: Improvement > Reporter: Xiang Li > Assignee: Xiang Li > Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-18022.master.000.patch > > > Regarding the following error message > bq. ERROR: java.io.IOException: org.apache.hadoop.hbase.TableNotFoundException: Table 'hbase:acl' was not found, got: table1. > It is not clear. Users have no idea what it means and have to check the code and find that it is issued by ConnectionImplementation#locateRegionInMeta() when the table inputted is not the same as the one fetched from meta. -- This message was sent by Atlassian JIRA (v6.3.15#6346)