Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 4FED611CD8 for ; Tue, 15 Jul 2014 10:06:48 +0000 (UTC) Received: (qmail 53510 invoked by uid 500); 15 Jul 2014 10:06:43 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 53404 invoked by uid 500); 15 Jul 2014 10:06:43 -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 53384 invoked by uid 99); 15 Jul 2014 10:06:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jul 2014 10:06:43 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of praveenesh@gmail.com designates 209.85.219.41 as permitted sender) Received: from [209.85.219.41] (HELO mail-oa0-f41.google.com) (209.85.219.41) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jul 2014 10:06:39 +0000 Received: by mail-oa0-f41.google.com with SMTP id j17so2846055oag.28 for ; Tue, 15 Jul 2014 03:06:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nN9OVfpz6AmjD/unvLIvNMeE6voQFd0Pc7qxlQvZPqg=; b=kUh0wN2RSUxCFlrFUkACnnZYTKqk9ImDcESKPV3IYqIYUhR0df8qAm6bJpqQoNamPU C3zXX1/brqRyDRYlCUCQNz2CXiAheI0HVH55/XB1RrfUNobLsZU1yTL5zNBe51N/3v49 beAb8/k1VgXKkbPNEmwmGz8DxPqjB4OiPfopkVjqQsObtip5XoAhd2btNRXWRfnEgHKQ n5GJtqzGUvsC3/nkcOauJSGqoKP8DzDJKH2Qr3g6aGAZm3Fceb1wK88uYmataYRCCpim Lc6FtLH1892RWpRFW+2y8/iY9DctdBCA4kNjYMdYOGeeUO+RC58UjH1nx/b6Y5rqkgai kQ7Q== MIME-Version: 1.0 X-Received: by 10.60.52.115 with SMTP id s19mr5374679oeo.21.1405418772308; Tue, 15 Jul 2014 03:06:12 -0700 (PDT) Received: by 10.182.133.33 with HTTP; Tue, 15 Jul 2014 03:06:12 -0700 (PDT) In-Reply-To: References:

Date: Tue, 15 Jul 2014 11:06:12 +0100 Message-ID: Subject: Re: HDFS multi-tenancy and federation From: praveenesh kumar To: "user@hadoop.apache.org" Cc: hdfs-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a11331132af296004fe388e93 X-Virus-Checked: Checked by ClamAV on apache.org --001a11331132af296004fe388e93 Content-Type: text/plain; charset=UTF-8 Federation is just a namenode namespace management capability. It is designed to control namenode management and to provide scalability for namenode. I don't think it poses any security or restrictions on accesssing the HDFS filesystem. I guess this link would help for your question 2 - http://hadoop.apache.org/docs/r2.4.0/hadoop-project-dist/hadoop-hdfs/ViewFs.html On Tue, Jul 15, 2014 at 10:06 AM, Shani Ranasinghe wrote: > Hi, > > Thanks for the information. > > Can I have an answer for the question 2 please? Appreciate any help. > > > On Wed, Feb 5, 2014 at 1:41 PM, praveenesh kumar > wrote: > >> Hi Shani, >> >> I haven't done any implementation on HDFS federation, but as far as I >> know, 1 namenode can handle only 1 namespace at this time. I hope that >> helps. >> >> Regards >> Prav >> >> >> On Wed, Feb 5, 2014 at 8:05 AM, Shani Ranasinghe >> wrote: >> >>> Hi, >>> >>> Any help on this please? >>> >>> >>> >>> On Mon, Feb 3, 2014 at 12:14 PM, Shani Ranasinghe >>> wrote: >>> >>>> >>>> Hi, >>>> I would like to know the following. >>>> >>>> 1) Can there be multiple namespaces in a single namenode? is it >>>> recommended? (I'm having a multi-tenant environment in mind) >>>> >>>> 2) Let's say I have a federated namespace/namenodes. There are two >>>> namenodes A /namespace A1 and namenode B/namespace B1, and have 3 >>>> datanodes. Can someone from namespace A1, access the datanode's data in >>>> anyway (hacking) belonging to namespace B1. If not how is it handled? >>>> >>>> After going through a lot of reference, my understanding on HDFS >>>> multi-tenancy and federation is that for multi-tenancy what we could do is >>>> use file/folder permissions (u,g,o) and ACL's. Or we could dedicate a >>>> namespace per tenant. The issue here is that a namenode (active namenode, >>>> passive namenode and secondary namenode) has to be assigned per tenant. Is >>>> there any other way that multi tenancy can be achieved? >>>> >>>> On federation, let's say I have a namenode for /marketing and another >>>> for /finance. Lets say that marketing bears the most load. How can we load >>>> balance this? is it possible? >>>> >>>> Appreciate any help on this. >>>> >>>> Regards, >>>> Shani. >>>> >>>> >>>> >>>> >>> >> > --001a11331132af296004fe388e93 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Federation is just a namenode namespace man= agement capability. It is designed to control namenode management and to pr= ovide scalability for namenode. I don't think it poses any security or = restrictions on accesssing the HDFS filesystem. I guess this link would hel= p for your question 2 - http://hadoop.apache.org/docs/r2.= 4.0/hadoop-project-dist/hadoop-hdfs/ViewFs.html

On Tue, Jul 15, 2014 at 10:06 = AM, Shani Ranasinghe <shanira14@gmail.com> wrote:

Hi,

= Thanks for the information.

Can I have an answer for the ques= tion 2=C2=A0 please? Appreciate any help.

On Wed, Feb 5, 2014 at 1:41 PM, praveenesh= kumar <praveenesh@gmail.com> wrote:

Hi Shani,

I haven't done any implementation on HDFS federation, but as far = as I know, 1 namenode can handle only 1 namespace at this time. I hope that= helps.

Regards

Prav

On Wed, Feb 5, 2014 at 8:05 AM, Shani Ranasingh= e <shanira14@gmail.com> wrote:

Hi,

Any h= elp on this please?

On Mon, Feb 3, 2014 at 12:14 PM, Shani R= anasinghe <shanira14@gmail.com> wrote:

Hi,
I would like to know the following.

1) Can there be multi= ple namespaces in a single namenode? is it recommended?=C2=A0 (I'm havi= ng a multi-tenant environment in mind)

2) Let's say I have a federated namespace/namenodes. The= re are two namenodes A /namespace A1 and namenode B/namespace B1, and have = 3 datanodes. Can someone from namespace A1,=C2=A0 access the datanode's= data in anyway (hacking) belonging to namespace B1. If not how is it handl= ed?

After going through a lot=C2=A0 of reference, my understanding on= HDFS multi-tenancy and federation is that for multi-tenancy what we could = do is use file/folder permissions (u,g,o) and ACL's. Or we could dedica= te a namespace per tenant. The issue here is that a namenode (active nameno= de, passive namenode and secondary namenode) has to be assigned per tenant.= =C2=A0 Is there any other way that multi tenancy can be achieved?

On federation, let's say I have a namenode for /marketin= g and another for /finance. Lets say that marketing bears the most load. Ho= w can we load balance this? is it possible?

Appreciate an= y help on this.

Regards,
Shani.

--001a11331132af296004fe388e93--