[
https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14951090#comment-14951090
]
Hudson commented on HDFS-9142:
------------------------------
FAILURE: Integrated in Hadoop-Yarn-trunk #1242 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/1242/])
HDFS-9142. Separating Configuration object for namenode(s) in (mingma: rev
de8efc65a455c10ae7280b5982c48f9aca84c9d4)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestMiniDFSCluster.java
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/MiniDFSCluster.java
> Separating Configuration object for namenode(s) in MiniDFSCluster
> -----------------------------------------------------------------
>
> Key: HDFS-9142
> URL: https://issues.apache.org/jira/browse/HDFS-9142
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Siqi Li
> Assignee: Siqi Li
> Fix For: 2.8.0
>
> Attachments: HDFS-9142-branch-2.v1.patch, HDFS-9142.v1.patch,
> HDFS-9142.v2.patch, HDFS-9142.v3.patch, HDFS-9142.v4.patch,
> HDFS-9142.v5.patch, HDFS-9142.v6.patch, HDFS-9142.v7.patch
>
>
> When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode
> should have its own configuration object, and the configuration should have
> "dfs.namenode.http-address-<nameservice>-<namenodeid>" set up correctly for
> all <nameserivce, namenodeid> pair
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
