hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6313) WebHdfs may use the wrong NN when configured for multiple HA NNs
Date Sat, 10 May 2014 22:12:38 GMT

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

Daryn Sharp commented on HDFS-6313:
-----------------------------------

Looks good.  Should the test clone the conf for the client before injecting another logical
name to ensure it doesn't cause side-effects in the minicluster?

> WebHdfs may use the wrong NN when configured for multiple HA NNs
> ----------------------------------------------------------------
>
>                 Key: HDFS-6313
>                 URL: https://issues.apache.org/jira/browse/HDFS-6313
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>    Affects Versions: 3.0.0, 2.4.0
>            Reporter: Daryn Sharp
>            Assignee: Kihwal Lee
>            Priority: Blocker
>             Fix For: 3.0.0, 2.4.1
>
>         Attachments: HDFS-6313.branch-2.4.patch, HDFS-6313.patch
>
>
> WebHdfs resolveNNAddr will return a union of addresses for all HA configured NNs.  The
client may access the wrong NN.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message