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 1D87D200C7F for ; Wed, 24 May 2017 21:41:13 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1C29B160BD0; Wed, 24 May 2017 19:41:13 +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 638C2160BA5 for ; Wed, 24 May 2017 21:41:12 +0200 (CEST) Received: (qmail 88936 invoked by uid 500); 24 May 2017 19:41:11 -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 88922 invoked by uid 99); 24 May 2017 19:41:11 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 May 2017 19:41:11 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id DBF47C4423 for ; Wed, 24 May 2017 19:41:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id OyGumb4IQTKC for ; Wed, 24 May 2017 19:41:10 +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 D8C455FC4D for ; Wed, 24 May 2017 19:41:09 +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 7A75AE0C0F for ; Wed, 24 May 2017 19:41:09 +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 2EE112193A for ; Wed, 24 May 2017 19:41:09 +0000 (UTC) Date: Wed, 24 May 2017 19:41:09 +0000 (UTC) From: "Hanisha Koneru (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-11877) FileJournalManager#getLogFile should ignore in progress edit logs during JN sync MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 24 May 2017 19:41:13 -0000 [ https://issues.apache.org/jira/browse/HDFS-11877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanisha Koneru updated HDFS-11877: ---------------------------------- Description: Due to synchronization introduced in HDFS-4025, a journal might have an edit log and an in progress edit log with the same start tx id. This would create an exception if GetJournalEditServlet tries to download edit with that start tx id from FileJournalManager. JournalNodeSyncer can fail when trying to fetch an edit log in this scenario. FileJournalManager#getLogFile should ignore in progress edit logs for JN sync downloads. was: Due to synchronization introduced in HDFS-4025, a journal might have an edit log and an in progress edit log with the same start tx id. This would create an exception if GetJournalEditServlet tries to download edit with that start tx id from FileJournalManager. JournalNodeSyncer can fail when trying to fetch an edit log in this scenario. FileJournalManager#getLogFile should have an option to specify whether in progress edit logs should be considered or not. > FileJournalManager#getLogFile should ignore in progress edit logs during JN sync > -------------------------------------------------------------------------------- > > Key: HDFS-11877 > URL: https://issues.apache.org/jira/browse/HDFS-11877 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs > Reporter: Hanisha Koneru > Assignee: Hanisha Koneru > > Due to synchronization introduced in HDFS-4025, a journal might have an edit log and an in progress edit log with the same start tx id. This would create an exception if GetJournalEditServlet tries to download edit with that start tx id from FileJournalManager. JournalNodeSyncer can fail when trying to fetch an edit log in this scenario. > FileJournalManager#getLogFile should ignore in progress edit logs for JN sync downloads. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org