[
https://issues.apache.org/jira/browse/HDFS-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001751#comment-13001751
]
Jitendra Nath Pandey commented on HDFS-1689:
--------------------------------------------
Steps to configure federated namenodes in hdfs-site.xml:
1. For every namenode in the system, choose a nameServiceID. Example:
nameservice1, nameservice2 etc..
2. Add list of comma separated nameServiceIDs to "dfs.federation.nameservices".
3. Add parameters that need to be specifically configured for a namenode, with
corresponding nameServiceID suffix and
with values.
4. Do the step 3 for secondary namenode/backup/checkpointer depending on your
installation.
5. On namenodes, secondary namenode/backup/checkpointer, do one of the
following:
- Configure dfs.federation.nameservice.id to corresponding nameServiceID in
hdfs-site.xml.
- Alternatively, you could pass on these nodes
-Ddfs.federation.nameservice=<nameServiceID>.
> Hdfs Federation: Configuration for namenodes
> --------------------------------------------
>
> Key: HDFS-1689
> URL: https://issues.apache.org/jira/browse/HDFS-1689
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: name-node
> Affects Versions: Federation Branch
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Fix For: Federation Branch
>
> Attachments: HDFS-1689.1.patch, HDFS-1689.2.patch
>
>
> We need ability to specify some configuration parameters which are namenode
> specific.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
