From hdfs-dev-return-14137-apmail-hadoop-hdfs-dev-archive=hadoop.apache.org@hadoop.apache.org Thu May 29 09:16:03 2014 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 6E83010FE1 for ; Thu, 29 May 2014 09:16:03 +0000 (UTC) Received: (qmail 97734 invoked by uid 500); 29 May 2014 09:16:02 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 97633 invoked by uid 500); 29 May 2014 09:16: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 97624 invoked by uid 99); 29 May 2014 09:16: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 09:16:02 +0000 Date: Thu, 29 May 2014 09:16:02 +0000 (UTC) From: "Dian Fu (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-6467) Format mirror cluster with primary cluster's NamespaceInfo in the runtime MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Dian Fu created HDFS-6467: ----------------------------- Summary: Format mirror cluster with primary cluster's NamespaceInfo in the runtime Key: HDFS-6467 URL: https://issues.apache.org/jira/browse/HDFS-6467 Project: Hadoop HDFS Issue Type: Sub-task Affects Versions: 3.0.0 Reporter: Dian Fu Fix For: 3.0.0 When a DFSClient write data to datanodes, it will specify a block pool id which is used by datanodes to distinguish the federation this data belongs to. We know that block pool id is generated by namenode when doing format, so different namenodes will have different block pool id. In the sync mode of DR, a DFSClient in the primary cluster will write data to Datanodes both in primary cluster and mirror cluster. So we need guarantee that the block pool id of primary cluster and mirror cluster are the same. -- This message was sent by Atlassian JIRA (v6.2#6252)