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 B129D9015 for ; Sat, 15 Oct 2011 17:57:20 +0000 (UTC) Received: (qmail 44598 invoked by uid 500); 15 Oct 2011 17:57:19 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 44495 invoked by uid 500); 15 Oct 2011 17:57:19 -0000 Mailing-List: contact hdfs-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-user@hadoop.apache.org Delivered-To: mailing list hdfs-user@hadoop.apache.org Received: (qmail 44481 invoked by uid 99); 15 Oct 2011 17:57:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Oct 2011 17:57:19 +0000 X-ASF-Spam-Status: No, hits=1.6 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sesha911@gmail.com designates 209.85.210.176 as permitted sender) Received: from [209.85.210.176] (HELO mail-iy0-f176.google.com) (209.85.210.176) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Oct 2011 17:57:13 +0000 Received: by iakh37 with SMTP id h37so5706051iak.35 for ; Sat, 15 Oct 2011 10:56:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=34022pe3rz4RNlCg6eYyP2LX62cfYR9p0fR4ODDCpGI=; b=rajHkXzyptlGAi85soVe1vHBB/Ov2AISROU5ZBrIep0AHkBR/UvG0npSN3YlVBg3fv yfsD3Sw297llUeJGwrPt6GIm6xXZLaGhho4wWYBNSxfNwCg1ZhE1BIXWDSDaJxZVWCrM 7BIJhDh9oRqOWXiD0pbp42I9If7vEAdbUm6XM= MIME-Version: 1.0 Received: by 10.42.147.196 with SMTP id o4mr25845859icv.33.1318701413005; Sat, 15 Oct 2011 10:56:53 -0700 (PDT) Received: by 10.42.165.131 with HTTP; Sat, 15 Oct 2011 10:56:52 -0700 (PDT) In-Reply-To: <6B049D97-CB75-4FF2-865A-58317D06A964@cloudera.com> References: <6B049D97-CB75-4FF2-865A-58317D06A964@cloudera.com> Date: Sat, 15 Oct 2011 23:26:52 +0530 Message-ID: Subject: Re: HDFS small files From: Sesha Kumar To: hdfs-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=90e6ba613bf0497d1c04af5a1975 --90e6ba613bf0497d1c04af5a1975 Content-Type: text/plain; charset=ISO-8859-1 Thanks a lot. But i still got this doubt like... will the namenodes in federation model have same configuration with respect to memory and other things as the ones before federation model?(single-namenode-for-a-cluster model) Wont there be bottle neck if am gonna access 1 single namespace for like a 1000times for some files? how is that handled? Thanks in advance --90e6ba613bf0497d1c04af5a1975 Content-Type: text/html; charset=ISO-8859-1 Thanks a lot.

But i still got this doubt like... will the namenodes in federation model have same configuration with respect to memory and other things as the ones before federation model?(single-namenode-for-a-cluster model)
Wont there be bottle neck if am gonna access 1 single namespace for like a 1000times for some files? how is that handled?

Thanks in advance
--90e6ba613bf0497d1c04af5a1975--