hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ming Ma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9142) Separating Configuration object for namenode(s) in MiniDFSCluster
Date Fri, 09 Oct 2015 18:18:09 GMT

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

Ming Ma commented on HDFS-9142:

+1 on the latest patch. I have committed to trunk. However it doesn't apply to branch-2. [~l201514]
can you provide a patch for branch-2?

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

View raw message