From dev-return-50086-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Mon Mar 12 19:19:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id ECBDD18064D for ; Mon, 12 Mar 2018 19:19:04 +0100 (CET) Received: (qmail 564 invoked by uid 500); 12 Mar 2018 18:19:03 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 553 invoked by uid 99); 12 Mar 2018 18:19:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Mar 2018 18:19:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 50CF91A08F8 for ; Mon, 12 Mar 2018 18:19:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -101.511 X-Spam-Level: X-Spam-Status: No, score=-101.511 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id iWKEgDH480m2 for ; Mon, 12 Mar 2018 18:19:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 1919F5F2EC for ; Mon, 12 Mar 2018 18:19:02 +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 39D9EE0226 for ; Mon, 12 Mar 2018 18:19:01 +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 9FD092147C for ; Mon, 12 Mar 2018 18:19:00 +0000 (UTC) Date: Mon, 12 Mar 2018 18:19:00 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-3165) System table integrity check and repair tool MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-3165?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 395642#comment-16395642 ]=20 Andrew Purtell commented on PHOENIX-3165: ----------------------------------------- We have=C2=A0a need for something that finds orphan rows in syscat and remo= ves them. It could be an interesting occasion to start development of this = tool. For the moment the orphan check and repair could be the first and onl= y function. More to be added later.=C2=A0 I vote for calling this tool "phck" It can be pronounced as "pee-haich-cee-kay" or ... some other way...=C2=A0p= er your personal preference.=C2=A0Maybe a bit on the nose but=C2=A0amusing = nonetheless. > System table integrity check and repair tool > -------------------------------------------- > > Key: PHOENIX-3165 > URL: https://issues.apache.org/jira/browse/PHOENIX-3165 > Project: Phoenix > Issue Type: New Feature > Reporter: Andrew Purtell > Priority: Critical > > When the Phoenix system tables become corrupt recovery is a painstaking p= rocess of low level examination of table contents and manipulation of same = with the HBase shell. This is very difficult work providing no margin of sa= fety, and is a critical gap in terms of usability. > At the OS level, we have fsck. > At the HDFS level, we have fsck (integrity checking only, though) > At the HBase level, we have hbck.=20 > At the Phoenix level, we lack a system table repair tool.=20 > Implement a tool that: > - Does not depend on the Phoenix client. > - Supports integrity checking of SYSTEM tables. Check for the existence o= f all required columns in entries. Check that entries exist for all Phoenix= managed tables (implies Phoenix should add supporting advisory-only metada= ta to the HBase table schemas). Check that serializations are valid.=20 > - Supports complete repair of SYSTEM.CATALOG and recreation, if necessary= , of other tables like SYSTEM.STATS which can be dropped to recover from an= emergency. We should be able to drop SYSTEM.CATALOG (or any other SYSTEM t= able), run the tool, and have a completely correct recreation of SYSTEM.CAT= ALOG available at the end of its execution. > - To the extent we have or introduce cross-system-table invariants, check= them and offer a repair or reconstruction option. -- This message was sent by Atlassian JIRA (v7.6.3#76005)