From hdfs-issues-return-230434-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Thu Aug 23 11:13:03 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 2E80218061A for ; Thu, 23 Aug 2018 11:13:03 +0200 (CEST) Received: (qmail 91289 invoked by uid 500); 23 Aug 2018 09:13:02 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 91278 invoked by uid 99); 23 Aug 2018 09:13:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Aug 2018 09:13:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id AFAD8C0FE1 for ; Thu, 23 Aug 2018 09:13:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id LIGtlJlc5C0c for ; Thu, 23 Aug 2018 09:13:01 +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 EC1C15F1B9 for ; Thu, 23 Aug 2018 09:13:00 +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 6B987E0101 for ; Thu, 23 Aug 2018 09:13:00 +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 2B2BF23F98 for ; Thu, 23 Aug 2018 09:13:00 +0000 (UTC) Date: Thu, 23 Aug 2018 09:13:00 +0000 (UTC) From: "Adam Antal (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-13818) Extend OIV to detect FSImage corruption 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/HDFS-13818?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1658= 9941#comment-16589941 ]=20 Adam Antal commented on HDFS-13818: ----------------------------------- Patch v1 uploaded, waiting for jenkins. Tests for the new processor not yet included - also not sure how it should = be tested. > Extend OIV to detect FSImage corruption > --------------------------------------- > > Key: HDFS-13818 > URL: https://issues.apache.org/jira/browse/HDFS-13818 > Project: Hadoop HDFS > Issue Type: Improvement > Components: hdfs > Reporter: Adam Antal > Assignee: Adam Antal > Priority: Major > Attachments: HDFS-13818.001.patch > > > A follow-up Jira for=C2=A0HDFS-13031: an improvement of the OIV is sugges= ted for detecting corruptions like=C2=A0HDFS-13101 in an offline way. > The reasoning is the following. Apart from a NN startup throwing the erro= r, there is nothing in the customer's hand that could reassure him/her that= the FSImages is good or corrupted. > Although real full checking of the FSImage is only possible by the NN, fo= r stack traces associated with the observed corruption cases the solution o= f putting up a tertiary NN is a little bit of overkill.=C2=A0The OIV would = be a handy choice,=C2=A0already having functionality like loading the fsima= ge and constructing the folder structure, we just have to add the option of= detecting the null INodes. For e.g. the Delimited OIV processor can alread= y use in disk MetadataMap, which reduces memory consumption. Also there may= be a window for parallelizing: iterating through INodes for e.g. could be = done distributed, increasing efficiency, and we wouldn't need a high mem-hi= gh CPU setup for just checking the FSImage. > The suggestion is to add a --detectCorruption option to the OIV which wou= ld check the FSImage for consistency. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org