Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EB79510F58 for ; Thu, 29 May 2014 08:58:02 +0000 (UTC) Received: (qmail 68948 invoked by uid 500); 29 May 2014 08:58:02 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 68777 invoked by uid 500); 29 May 2014 08:58:02 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 68672 invoked by uid 99); 29 May 2014 08:58:02 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 May 2014 08:58:02 +0000 Date: Thu, 29 May 2014 08:58:01 +0000 (UTC) From: "Dian Fu (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-6465) Enable the configuration of multiple clusters MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Dian Fu created HDFS-6465: ----------------------------- Summary: 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 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: ... 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: .. -- This message was sent by Atlassian JIRA (v6.2#6252)