Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B1B2B10B18 for ; Thu, 30 Jan 2014 15:26:30 +0000 (UTC) Received: (qmail 46616 invoked by uid 500); 30 Jan 2014 15:26:22 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 46329 invoked by uid 500); 30 Jan 2014 15:26:12 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 46060 invoked by uid 99); 30 Jan 2014 15:26:10 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jan 2014 15:26:10 +0000 Date: Thu, 30 Jan 2014 15:26:10 +0000 (UTC) From: "Vinay (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-5855) Reading edits should not stop at UpgradeMarker for normal restart of the namenode MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Vinay created HDFS-5855: --------------------------- Summary: Reading edits should not stop at UpgradeMarker for normal restart of the namenode Key: HDFS-5855 URL: https://issues.apache.org/jira/browse/HDFS-5855 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Vinay As mentioned [here|https://issues.apache.org/jira/browse/HDFS-5645?focusedCommentId=13867530&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13867530] in HDFS-5645 NameNode restart will stop reading Edits at UpgradeMarker. But this should happen only if namenode is rolling back from upgrade. There is also a possibility that namenode could get restarted after rolling upgrade started. This should not rollback everything. -- This message was sent by Atlassian JIRA (v6.1.5#6160)