[
https://issues.apache.org/jira/browse/HDFS-6465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017388#comment-14017388
]
Vinayakumar B commented on HDFS-6465:
-------------------------------------
Hi [~dian.fu],
Please note, in Hadoop, we follow following conventions while updating fields
of Jira to avoid misunderstandings in future.
Affect versions - This has to be one of the released version (latest) where
the defect is present (Applicable only for Bugs, not for new feature),
indicating that bug was there in that version
Fix Versions- *This will be updated by the committer after committing the
changes*. This could be a branch version as well for subtasks during the
development in a separate branch.
Target Versions- Here contributor can set the unreleased targetted versions
where patch needs to be committed. In this Jira, you can set 3.0.0 value to
this field.
> Enable the configuration of multiple clusters
> ---------------------------------------------
>
> Key: HDFS-6465
> URL: https://issues.apache.org/jira/browse/HDFS-6465
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Affects Versions: DisasterRecovery (HDFS-5442)
> Reporter: Dian Fu
> Assignee: Dian Fu
> Fix For: 3.0.0
>
> Attachments: HDFS-6465.1.patch, HDFS-6465.2.patch, HDFS-6465.patch
>
>
> Tracks the changes required for configuration DR.
> configurations added:
> DFS_REGION_ID("dfs.region.id") : the region id of current cluster
> DFS_REGIONS("dfs.regions") : the region ids of all clusters, including
> both the primary cluster and mirror cluster
> DFS_REGION_PRIMARY("dfs.region.primary") : the region id of primary
> cluster
> configurations modified:
> The configurations in NAMENODE.NAMENODE_SPECIFIC_KEYS can be configured
> in the following format to distinguish between clusters.
> If a configuration with a region id as suffix cannot be found, the
> configuration without region id as suffix will be used instead:
> <configuration key>.<nameservice id>.<namenode id>.<region id>
> The configurations in NAMENODE.NAMESERVICE_SPECIFIC_KEYS can be configured in
> the following format to distinguish between clusters.
> If a configuration with a region id as suffix cannot be found, the
> configuration without region id as suffix will be used instead:
> <configuration key>.<nameservice id>.<region id>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
