Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4F90EDF97 for ; Wed, 15 May 2013 14:38:55 +0000 (UTC) Received: (qmail 17576 invoked by uid 500); 15 May 2013 14:38:50 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 17318 invoked by uid 500); 15 May 2013 14:38:50 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 17310 invoked by uid 99); 15 May 2013 14:38:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 May 2013 14:38:50 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of michael_segel@hotmail.com designates 65.55.111.103 as permitted sender) Received: from [65.55.111.103] (HELO blu0-omc2-s28.blu0.hotmail.com) (65.55.111.103) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 May 2013 14:38:42 +0000 Received: from BLU0-SMTP82 ([65.55.111.71]) by blu0-omc2-s28.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 15 May 2013 07:38:21 -0700 X-EIP: [5yd9c93RORNVIvKozAiNEZQGtkjA/XA/] X-Originating-Email: [michael_segel@hotmail.com] Message-ID: Received: from [172.25.48.227] ([173.252.71.2]) by BLU0-SMTP82.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 15 May 2013 07:38:19 -0700 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: =?windows-1252?Q?Re=3A_Question_about_Name_Spaces=85_?= From: Michael Segel In-Reply-To: <943DB4E9-848E-456D-A30D-F9D5FF4EA291@yahoo.com> Date: Wed, 15 May 2013 09:38:18 -0500 Content-Transfer-Encoding: quoted-printable References: <943DB4E9-848E-456D-A30D-F9D5FF4EA291@yahoo.com> To: user@hadoop.apache.org X-Mailer: Apple Mail (2.1503) X-OriginalArrivalTime: 15 May 2013 14:38:20.0024 (UTC) FILETIME=[D82FFF80:01CE5179] X-Virus-Checked: Checked by ClamAV on apache.org Well...=20 On the one hand, I'm trying to understand why one would break a cluster = in to multiple name spaces.=20 (Obviously this gets back to managing very large clusters.)=20 On the other. Why would someone want to have a copy of a file in two = different name spaces?=20 I'm making an assumption that when we have 3x replication that the = replicas don't cross name space boundaries. (Is this correct?) My take is that one would copy a file to a second name space because = they want a physical copy in both name spaces for redundancy in case a = name space goes down. They would do this only for mission critical = files, or if the data is being shared by two different groups who want = their own copy of the data and they work solely within a single name = space.=20 The reason I am asking is that I'm trying to see how people view and use = namespaces.=20 Does that make sense?=20 Thx On May 15, 2013, at 9:24 AM, Lohit wrote: >=20 >=20 > On May 15, 2013, at 7:17 AM, Michael Segel = wrote: >=20 >> Quick question... >> So when we have a cluster which has multiple namespaces (multiple = name nodes) , why would you have a file in two different namespaces?=20 >>=20 > Are you saying why one would create same file in two namespace? Or are = you saying is there an option to have only one file but in two = namespace?=20 >=20 > Could you rephrase or give more information=20 >>=20 >=20