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 38EF5CE5C for ; Tue, 8 May 2012 08:15:56 +0000 (UTC) Received: (qmail 61338 invoked by uid 500); 8 May 2012 08:15:53 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 60766 invoked by uid 500); 8 May 2012 08:15:46 -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 60706 invoked by uid 99); 8 May 2012 08:15:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 May 2012 08:15:43 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dennyy99@gmail.com designates 209.85.217.176 as permitted sender) Received: from [209.85.217.176] (HELO mail-lb0-f176.google.com) (209.85.217.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 May 2012 08:15:37 +0000 Received: by lboj14 with SMTP id j14so4739088lbo.35 for ; Tue, 08 May 2012 01:15:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=rwB4gvM8JCuUnHq6+D4wW20nyjS6vXHYO3E+MvhVoo8=; b=p0fYg7jTs60XzTrCJR98G0bcSHMrpD5guxYPZ7sSF6g4VpJlKl0ma0Z3tO+GuOgv2K qaGHAF+qsQWjauMUF/YOetJ3028jk8POGMPj9tqOf4w8cv+glbbrP/avNx/056J9ZdTR 25CJx59cYtGwqT9ACqWSSKE+og4baqC7JSJ6BCuZ7173v9RkwKPO6fFn7dL/dvJHs+bV pLSu6eaUcVauiCNSXsuk7v5YGuv9XVrztdipKKoS0+FsBOA0ubss/Ow2xuBgOwEvZupX JhR8l2x4AN9yIzTTw75hsJLClJA7GSbhBhDFQdqbNDy0RFW+FN0UEGuNdOsy5vAmvTRU eBqw== MIME-Version: 1.0 Received: by 10.152.103.109 with SMTP id fv13mr6886395lab.33.1336464915914; Tue, 08 May 2012 01:15:15 -0700 (PDT) Received: by 10.112.24.138 with HTTP; Tue, 8 May 2012 01:15:15 -0700 (PDT) Date: Tue, 8 May 2012 16:15:15 +0800 Message-ID: Subject: Does NameNode directory need fine-grained path lock? From: Denny Ye To: hdfs-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=f46d040890c791610d04bf81fc7d X-Virus-Checked: Checked by ClamAV on apache.org --f46d040890c791610d04bf81fc7d Content-Type: text/plain; charset=ISO-8859-1 hi guys, Currently, NameNode uses read-write lock at top root folder. In my opinion, it's too huge for whole namespace with million of file/folder. Meanwhile, a few level folder on top of the namespace directory has been set with different application. Does we need lesser lock level for such application sub-directory to reduce impact each other? It can be used with five(or less) top level to HDFS path with individual lock tree-like structure. Can anybody provide your feedback or advice? Thanks -Regards Denny Ye --f46d040890c791610d04bf81fc7d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable hi guys,=A0
=A0 =A0 Currently, NameNode uses read-write lock at top roo= t folder. In my opinion, it's too huge for whole namespace with million= of file/folder. Meanwhile, a few level folder on top of the namespace dire= ctory has been set with different application. Does we need lesser lock lev= el for such application sub-directory to reduce impact each other? It can b= e used with five(or less) top level to HDFS path with=A0individual lock tre= e-like structure.
=A0 =A0 =A0Can anybody provide your feedback or advice? Thanks

-Regards
Denny Ye
--f46d040890c791610d04bf81fc7d--