Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 11 Sep 2014 14:27:34 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12740790.1410444864000.9482.1410445654346@Atlassian.JIRA>
In-Reply-To: <JIRA.12740790.1410444864000@Atlassian.JIRA>
References: <JIRA.12740790.1410444864000@Atlassian.JIRA>
 <JIRA.12740790.1410444864933@arcas>
Subject: [jira] [Commented] (HDFS-7046) HA NN can NPE upon transition to
 active
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130079#comment-14130079 ] 

Aaron T. Myers commented on HDFS-7046:
--------------------------------------

Good find, Daryn. Given that you marked this as affecting 2.5.0, do you have reason to believe that this does not affect earlier versions?

> HA NN can NPE upon transition to active
> ---------------------------------------
>
>                 Key: HDFS-7046
>                 URL: https://issues.apache.org/jira/browse/HDFS-7046
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 3.0.0, 2.5.0
>            Reporter: Daryn Sharp
>            Priority: Critical
>
> While processing edits, the NN may decide after adjusting block totals to leave safe mode - in the middle of the edit.  Going active starts the secret manager which generates a new secret key, which in turn generates an edit, which NPEs because the edit log is not open.
> # Transitions should _not_ occur in the middle of an edit.
> # The edit log appears to claim it's open for write when the stream isn't even open


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)