You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2014/05/29 11:59:01 UTC

[jira] [Commented] (HDFS-6465) Enable the configuration of multiple clusters

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

Hadoop QA commented on HDFS-6465:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12647334/HDFS-6465.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7004//console

This message is automatically generated.

> 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
>            Reporter: Dian Fu
>            Assignee: Dian Fu
>         Attachments: 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)