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 04ACE10EDC for ; Tue, 28 Jan 2014 11:01:33 +0000 (UTC) Received: (qmail 62468 invoked by uid 500); 28 Jan 2014 11:01:24 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 62381 invoked by uid 500); 28 Jan 2014 11:01:24 -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 62366 invoked by uid 99); 28 Jan 2014 11:01:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jan 2014 11:01:22 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates 209.85.213.182 as permitted sender) Received: from [209.85.213.182] (HELO mail-ig0-f182.google.com) (209.85.213.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jan 2014 11:01:16 +0000 Received: by mail-ig0-f182.google.com with SMTP id uy17so1295379igb.3 for ; Tue, 28 Jan 2014 03:00:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=UBegh5948hXsR8WPBu1sQWkeqP4V5TzUqKoIgl+7nx8=; b=hdbl97yxvkpQUBiGkN7pVgY/Ics9TIeIvDMBcBI79JZ9IvpeduOoMfCfhYR17q4Z44 GRqmKueRYhYLS79f9WNaFRk3dhz3E+NlBWpc0dsTg60rjOmqK6sWKUtX9CvJqpO44D3A jtu8ZQXvNGiXSkbpabzq9m3p9Dplcq/T0i6rlu1Z/YQXyPP2the0KUDaed+2/3a4VY9P x3sIBK6DV1OfLHfKA05RE4wv7uIFcs3I6jTiB7g5oEViVm2VG8nbEkCYQ55Iq2dSV+XV 1HzizwjsF+dhQWR9B100jhhsyapCtu9O6rdpO4wGP3qujZYdS5H9EVP84+qS4kJm9vhD sBdw== X-Gm-Message-State: ALoCoQnmi6kpHYpjX6dGHYs3+5ndkO/yDVfczWTAD4S1lxQgpqaljGcJ1yC0kNGKegVMu7cjEnH8 X-Received: by 10.43.46.2 with SMTP id um2mr572830icb.46.1390906855999; Tue, 28 Jan 2014 03:00:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.61.97 with HTTP; Tue, 28 Jan 2014 03:00:35 -0800 (PST) In-Reply-To: References: From: Harsh J Date: Tue, 28 Jan 2014 16:30:35 +0530 Message-ID: Subject: Re: memory management module of Namenode To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi, The central class is FSNamesystem.java downwards. I'd advise drilling down from the NameNodeRpcServer sources at https://github.com/apache/hadoop-common/blob/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNodeRpcServer.java, for any client operation your curiosity wants to dive into. On Tue, Jan 28, 2014 at 4:14 PM, Chetan Agrawal wrote: > I read that the namenode keeps all the metadata record in main memory right > for fast access. > I want to study the code where the namenode is instructed to do so i.e. to > keep metadata record in main memory. where can i find the source code file > for this namenode memory management? i am using github and have > 'hadoop-common' repository. -- Harsh J