Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 6 Dec 2016 20:51:58 +0000 (UTC)
From: "Mingliang Liu (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13017347.1478110812000.454345.1481057518577@Atlassian.JIRA>
In-Reply-To: <JIRA.13017347.1478110812000@Atlassian.JIRA>
References: <JIRA.13017347.1478110812000@Atlassian.JIRA> <JIRA.13017347.1478110812761@arcas>
Subject: [jira] [Commented] (HDFS-11094) Send back HAState along with
 NamespaceInfo during a versionRequest as an optional parameter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 06 Dec 2016 20:52:00 -0000


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

Mingliang Liu commented on HDFS-11094:
--------------------------------------

Thanks for bringing this up. If we agree to revert [HDFS-5079] in [HDFS-11207], we can firstly revert this to avoid breaking the build in {{trunk}}. We need more input who evolved in [HDFS-5079] before reverting it. For {{branch-2}} I won't commit the current patch.

> Send back HAState along with NamespaceInfo during a versionRequest as an optional parameter
> -------------------------------------------------------------------------------------------
>
>                 Key: HDFS-11094
>                 URL: https://issues.apache.org/jira/browse/HDFS-11094
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>            Reporter: Eric Badger
>            Assignee: Eric Badger
>             Fix For: 3.0.0-alpha2
>
>         Attachments: HDFS-11094.001.patch, HDFS-11094.002.patch, HDFS-11094.003.patch, HDFS-11094.004.patch, HDFS-11094.005.patch, HDFS-11094.006.patch, HDFS-11094.007.patch, HDFS-11094.008.patch, HDFS-11094.009-b2.patch, HDFS-11094.009.patch
>
>
> The datanode should know which NN is active when it is connecting/registering to the NN. Currently, it only figures this out during its first (and subsequent) heartbeat(s) and so there is a period of time where the datanode is alive and registered, but can't actually do anything because it doesn't know which NN is active. A byproduct of this is that the MiniDFSCluster will become active before it knows what NN is active, which can lead to NPEs when calling getActiveNN(). 


--
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