hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-9112) Haadmin fails if multiple name service IDs are configured
Date Mon, 21 Sep 2015 19:01:04 GMT

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

Anu Engineer updated HDFS-9112:
    Attachment: HDFS-9112.001.patch

[~atm] Thanks for letting me know. [~templedf] I would appreciate if you can take a look at
this patch.

This patch fixes getNamenodeServiceAddr by looking at dfs.internal.nameservices and choosing
the right name if we have more than one name entry in dfs.nameservices.

Along with Unit tests, manually verified that haadmin command is now able to locate nameserver
URI if we have the setup described in HDFS-6376

> Haadmin fails if multiple name service IDs are configured
> ---------------------------------------------------------
>                 Key: HDFS-9112
>                 URL: https://issues.apache.org/jira/browse/HDFS-9112
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 2.7.1
>            Reporter: Anu Engineer
>            Assignee: Anu Engineer
>         Attachments: HDFS-9112.001.patch
> In HDFS-6376 we supported a feature for distcp that allows multiple NameService IDs to
be specified so that we can copy from two HA enabled clusters.
> That confuses haadmin command since we have a check in DFSUtil#getNamenodeServiceAddr
which fails if it finds more than 1 name in that property.

This message was sent by Atlassian JIRA

View raw message