Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 99381D65F for ; Tue, 18 Dec 2012 21:09:44 +0000 (UTC) Received: (qmail 89003 invoked by uid 500); 18 Dec 2012 21:09:39 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 88892 invoked by uid 500); 18 Dec 2012 21:09:39 -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 88882 invoked by uid 99); 18 Dec 2012 21:09:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2012 21:09:39 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cembree@gmail.com designates 209.85.216.44 as permitted sender) Received: from [209.85.216.44] (HELO mail-qa0-f44.google.com) (209.85.216.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2012 21:09:33 +0000 Received: by mail-qa0-f44.google.com with SMTP id z4so3761615qan.10 for ; Tue, 18 Dec 2012 13:09:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=ZP9VigcF/w68L7vx0bx1mitQpcIYi/tMfa/Z8Sgf804=; b=HbNHRtIcAJxGDQV63cL+HdM1JeHb//5pYbdZabS0jBq/1BsrtIGi1xpTvZ/hNXLgQJ PFbHmGHJrcTl/5OvpmtbqD0yjC4CH4MZ5/2Dgg1VCxqqug2EFBlE6y9rpx8Fa90ACNor R3Gkmoy1lu8rlMa1Ss+kVkKEIstMkoeC2SwwFlffrrP7/TZ2Hgt8Fp9cBXc7a79EOHMy 3PN/X/IRh9tKh00+T761TIgj2MDGq2NJ//ZtmJx9d/hDmoIQtBh2QozZMGgX7OlwqtPp wuBUC7ByAnV7j43Mzd1Um+nmSsZ9BYyonRKt2YxxeB4Iay+SnQ3MWqLcZAemXotcZn+C vNoQ== MIME-Version: 1.0 Received: by 10.224.195.136 with SMTP id ec8mr1374341qab.98.1355864952670; Tue, 18 Dec 2012 13:09:12 -0800 (PST) Received: by 10.49.59.134 with HTTP; Tue, 18 Dec 2012 13:09:12 -0800 (PST) Reply-To: chris@embree.us In-Reply-To: References: Date: Tue, 18 Dec 2012 16:09:12 -0500 Message-ID: Subject: Re: datanode write forwarding From: Chris Embree To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=20cf3005dcaede08d104d126e8cc X-Virus-Checked: Checked by ClamAV on apache.org --20cf3005dcaede08d104d126e8cc Content-Type: text/plain; charset=ISO-8859-1 Hi Jay, We'll need "real developer" expertise on this, but my understanding of the documentation is: Client talks to Name node to get Node/Block assignments, client then talks to node 1: write, fwd, node 2: write, fwd, node 3: write, ack node 2, node 2: ack node1, node 1: ack Client and Name Node. write includes data write and checksum, ack = report success. The fwd requests happen AFTER successful write and checksum. Hope this helps. Chris On Tue, Dec 18, 2012 at 3:56 PM, Jay Vyas wrote: > Hi : > > Do data nodes, when they receive write requests, forward the request to > the next datanode in the chain after appending to a file? Or rather, do the > write and forward asynchronously and at the same time? > > -- > Jay Vyas > http://jayunit100.blogspot.com > --20cf3005dcaede08d104d126e8cc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Jay,

We'll need "real developer" expert= ise on this, but my understanding of the documentation is:=A0
Client talks to Name node to get Node/Block assignments, =A0cli= ent then talks to node 1: write, fwd, node 2: write, fwd, node 3: write, ac= k node 2, node 2: ack node1, node 1: ack Client and Name Node.

write includes data write and checksum, ack =3D report = success. =A0The fwd requests happen AFTER successful write and checksum.

Hope this helps.
Chris



On Tue, Dec 18, 2012 at 3:56 PM, Jay Vyas <jayunit100@gmail.com>= wrote:
Hi :

Do data nodes, when they receive w= rite requests, forward the request to the next datanode in the chain after= appending to a file? Or rather, do the write and forward asynchronously an= d at the same time?

--20cf3005dcaede08d104d126e8cc--