From hdfs-issues-return-229484-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Tue Aug 14 12:28: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 4969618067A for ; Tue, 14 Aug 2018 12:28:05 +0200 (CEST) Received: (qmail 16802 invoked by uid 500); 14 Aug 2018 10:28:04 -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 16791 invoked by uid 99); 14 Aug 2018 10:28:04 -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; Tue, 14 Aug 2018 10:28:04 +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 CF4071A27DC for ; Tue, 14 Aug 2018 10:28:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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-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 ttWOTKNIjRuc for ; Tue, 14 Aug 2018 10:28: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 906845F48E for ; Tue, 14 Aug 2018 10:28: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 4385FE111B for ; Tue, 14 Aug 2018 10:28: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 A1E8423FA0 for ; Tue, 14 Aug 2018 10:28:00 +0000 (UTC) Date: Tue, 14 Aug 2018 10:28:00 +0000 (UTC) From: "Gabor Bota (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-13031) To detect fsimage corruption on the spot 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-13031?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1657= 9615#comment-16579615 ]=20 Gabor Bota commented on HDFS-13031: ----------------------------------- Thanks [~adam.antal] for working on this and for creating the new issue.=20 This issue can be closed because we found that using an OIV improvement for= this is a better solution than using a full-fledged NN loading the full fs= image. > To detect fsimage corruption on the spot > ---------------------------------------- > > Key: HDFS-13031 > URL: https://issues.apache.org/jira/browse/HDFS-13031 > Project: Hadoop HDFS > Issue Type: Improvement > Components: hdfs > Environment: =C2=A0 > Reporter: Yongjun Zhang > Assignee: Adam Antal > Priority: Major > > Since we fixed HDFS-9406, there are new cases reported from the field tha= t similar fsimage corruption happens. We need good fsimage + editlogs to re= play to reproduce the corruption. However, usually when the corruption is d= etected (at later NN restart), the good fsimage is already deleted. > We need to have a way to detect fsimage corruption on the spot. Currently= what I think we could do is: > # after SNN creates a new fsimage, it spawn a new modified NN process (N= N with some new command line args) to just load the fsimage and do nothing = else.=C2=A0 > # If the process failed, the currently running SNN will do either a) bac= kup the fsimage + editlogs or b) no longer do checkpointing. And it need to= somehow raise a flag to user that the fsimage is corrupt. > In step 2, if we do a, we need to introduce new NN->JN API to backup edit= logs; if we do b, it changes SNN's behavior, and kind of not compatible.=C2= =A0 -- 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