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 5D049200AF7 for ; Tue, 14 Jun 2016 17:52:03 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5BAA5160A06; Tue, 14 Jun 2016 15:52:03 +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 A507A160A47 for ; Tue, 14 Jun 2016 17:52:02 +0200 (CEST) Received: (qmail 83786 invoked by uid 500); 14 Jun 2016 15:52:01 -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 83732 invoked by uid 99); 14 Jun 2016 15:52:01 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jun 2016 15:52:01 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 4EA252C1F69 for ; Tue, 14 Jun 2016 15:52:01 +0000 (UTC) Date: Tue, 14 Jun 2016 15:52:01 +0000 (UTC) From: "Kihwal Lee (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-10519) Add a configuration option to enable in-progress edit log tailing MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 14 Jun 2016 15:52:03 -0000 [ https://issues.apache.org/jira/browse/HDFS-10519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329706#comment-15329706 ] Kihwal Lee commented on HDFS-10519: ----------------------------------- How does it actually work? Can it replay the same edit log segment multiple times? It might have to replay the same in-progress segment multiple times or after it is finalized. I thought it would blow up with {{MetaRecoveryContext}} being null. > Add a configuration option to enable in-progress edit log tailing > ----------------------------------------------------------------- > > Key: HDFS-10519 > URL: https://issues.apache.org/jira/browse/HDFS-10519 > Project: Hadoop HDFS > Issue Type: Improvement > Components: ha > Reporter: Jiayi Zhou > Assignee: Jiayi Zhou > Priority: Minor > Attachments: HDFS-10519.001.patch, HDFS-10519.002.patch > > > Standby Namenode has the option to do in-progress edit log tailing to improve the data freshness. In-progress tailing is already implemented, but it's not enabled as default configuration. And there's no related configuration key to turn it on. > Adding a related configuration key to let Standby Namenode is reasonable and would be a basis for further improvement on Standby Namenode. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org