Return-Path: Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: (qmail 8356 invoked from network); 1 Apr 2010 15:50:53 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Apr 2010 15:50:53 -0000 Received: (qmail 67448 invoked by uid 500); 1 Apr 2010 15:50:52 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 67385 invoked by uid 500); 1 Apr 2010 15:50:52 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 67377 invoked by uid 99); 1 Apr 2010 15:50:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 15:50:51 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jaybooth@gmail.com designates 74.125.83.48 as permitted sender) Received: from [74.125.83.48] (HELO mail-gw0-f48.google.com) (74.125.83.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 15:50:43 +0000 Received: by gwaa12 with SMTP id a12so178898gwa.35 for ; Thu, 01 Apr 2010 08:50:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type; bh=xqdg+/AS03Ijy5hk5VISjz0i3Hz7GH4+zYxaU5OPtuw=; b=Gs9d9OzN7XWLjClH6au1oWrx5IHkgcEaJrRs661hqd+gqkjuS0iPqhUWAK6I8afWYm 1TNAcxgIRmVEZaSP7L+niu45d0j5uCqQmFD4T/G+5Svjd54MGrYTfqj5oRlUdzUclff/ wnKGhv+gNbfRD0TDQFeNmhgmLpDFu/XwXd7p8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=SZjzILtAUpSImNjZFd2XH5gS3CC49QzsZFlkK/t57dWEICG7jY6TK05NhDgoG7xA8L 5NN/TU1lroTAVEsJY5pIoPP3V/P/NmW5szJTvCIRswpdfUhUMVuUIwoM7Jxi7lZMVzlU /e+WBv5kjwE6LMp8YtvwR9OF9v26ixpY4LIwM= MIME-Version: 1.0 Received: by 10.100.201.9 with HTTP; Thu, 1 Apr 2010 08:50:22 -0700 (PDT) In-Reply-To: References: Date: Thu, 1 Apr 2010 11:50:22 -0400 Received: by 10.101.108.9 with SMTP id k9mr3026886anm.126.1270137022786; Thu, 01 Apr 2010 08:50:22 -0700 (PDT) Message-ID: Subject: Re: HDFS Blockreport question From: Jay Booth To: hdfs-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary=001636eee3840f2e4b04832ed2f7 X-Virus-Checked: Checked by ClamAV on apache.org --001636eee3840f2e4b04832ed2f7 Content-Type: text/plain; charset=ISO-8859-1 In DataNode: public DatanodeProtocol namenode It's not a reference to an actual namenode, it's a wrapper for a network protocol created by that RPC.waitForProxy call -- so when it calls namenode.blockReport, it's sending that information over RPC to the namenode instance over the network On Thu, Apr 1, 2010 at 5:50 AM, Alberich de megres wrote: > Hi everyone! > > sailing throught the hdfs source code that comes with hadoop 0.20.2, i > could not understand how hdfs sends blockreport to nameNode. > > As i can see, in > src/hdfs/org/apache/hadoop/hdfs/server/datanode/DataNode.java we > create this.namenode interface with RPC.waitForProxy call (wich i > could not understand which class it instantiates, and how it works). > > After that, datanode generates block list report (blockListAsLongs) > with data.getBlockReport, and call this.namenode.blockReport(..), > inside namenode.blockReport it calls again namesystem.processReport. > This leads to an update of block lists inside nameserver. > > But how it sends over the network this blockreport? > > Anyone can point me some light? > > thanks for all! > (and sorry for the newbie question) > > Alberich > --001636eee3840f2e4b04832ed2f7--