Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 91195 invoked from network); 13 Aug 2010 01:21:34 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Aug 2010 01:21:34 -0000 Received: (qmail 29603 invoked by uid 500); 13 Aug 2010 01:21:32 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 29569 invoked by uid 500); 13 Aug 2010 01:21:31 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 29561 invoked by uid 99); 13 Aug 2010 01:21:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Aug 2010 01:21:31 +0000 X-ASF-Spam-Status: No, hits=2.8 required=10.0 tests=FREEMAIL_FROM,HK_RANDOM_ENVFROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of zjffdu@gmail.com designates 74.125.82.176 as permitted sender) Received: from [74.125.82.176] (HELO mail-wy0-f176.google.com) (74.125.82.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Aug 2010 01:21:25 +0000 Received: by wyb35 with SMTP id 35so2938821wyb.35 for ; Thu, 12 Aug 2010 18:21:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=EPzoG7OMaTP/ttcWrv6PJF3+wwnhswmwmxkorPZC1NY=; b=PNMy/bpfQ0hDa/vixrW9xmz2srqRVQ78f7A71nll8CsJDHFjCR9hueDDOZH1fM/E/6 cFAIsXERJoGcZf6xg61nUwe6k+lWgSOi7YNi7s2tA8KnWEk/TI0gpv1PMdV70uFjJClq O2ejHlL5theaPyDLzWv4GbhmpVSs2rhyJdmAY= 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=ESj58ifkgnJKuWQAbfJsXd2LhUYj2nVk42xqL4GWv3Ec2xaVqUYmSrw/vA4HelaHQf gGF3EWL7TDYJ7S0tYoDzC/0FGOLvU5ZK31QK+iq/Bxhpir1fiY/W8hXfclPCpfCiTjRk WqcPfoMV8tO0Tro0PyORvnfVoRNiqYz7xlm9w= MIME-Version: 1.0 Received: by 10.216.176.83 with SMTP id a61mr651651wem.47.1281662464018; Thu, 12 Aug 2010 18:21:04 -0700 (PDT) Received: by 10.216.155.67 with HTTP; Thu, 12 Aug 2010 18:21:03 -0700 (PDT) In-Reply-To: References: Date: Fri, 13 Aug 2010 09:21:03 +0800 Message-ID: Subject: Re: hadoop RPC Server and Client From: Jeff Zhang To: common-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016e65aeed6e3d2ad048daa4b86 --0016e65aeed6e3d2ad048daa4b86 Content-Type: text/plain; charset=UTF-8 There's heartbeat between jobtracker and tasktracker, namenode and datanode. Besides, tasktracker will report task progress info to jobtracker, and datanode will report block report to namenode. On Fri, Aug 13, 2010 at 7:39 AM, Ahmad Shahzad wrote: > Hi ALL, > Can anyone tell me the purpose for RPC server and RPC client > that is used in hadoop. As far as logs tell, they are used by JobTracker > and > TaskTracker, as well as namenode and datanode. Can anyone tell me that for > what purpose RPC server and client are used by each of them. > > Ahmad > -- Best Regards Jeff Zhang --0016e65aeed6e3d2ad048daa4b86--