[ 
https://issues.apache.org/jira/browse/HDFS-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mingliang Liu updated HDFS-11094:
---------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0-alpha2
                   2.9.0
           Status: Resolved  (was: Patch Available)

Test failures are not related.

Committed to {{branch-2}} and {{trunk}} branches. Resolving this (again). 
Thanks all for the contribution.

> 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: 2.9.0, 3.0.0-alpha2
>
>         Attachments: HDFS-11094-branch-2.011.patch, 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, 
> HDFS-11094.010-b2.patch, HDFS-11094.010.patch, HDFS-11094.011.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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to