Return-Path: 
 <user-return-7976-apmail-hadoop-mapreduce-user-archive=hadoop.apache.org@hadoop.apache.org>
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 A57AFD4D7
	for <apmail-hadoop-mapreduce-user-archive@minotaur.apache.org>;
 Fri, 17 May 2013 17:11:36 +0000 (UTC)
Received: (qmail 28096 invoked by uid 500); 17 May 2013 17:11:32 -0000
Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org
Received: (qmail 27962 invoked by uid 500); 17 May 2013 17:11:31 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 27954 invoked by uid 99); 17 May 2013 17:11:31 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 May 2013 17:11:31 +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 rahul.rec.dgp@gmail.com
 designates 209.85.128.180 as permitted sender)
Received: from [209.85.128.180] (HELO mail-ve0-f180.google.com)
 (209.85.128.180)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 May 2013 17:11:26 +0000
Received: by mail-ve0-f180.google.com with SMTP id c13so1569362vea.25
        for <user@hadoop.apache.org>; Fri, 17 May 2013 10:11:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=x-received:mime-version:from:date:message-id:subject:to
         :content-type;
        bh=1Wd5Y05UPe29+ULbNGAFyk+Lje8lpg1TX1nyPe27LfA=;
        b=G/l0PnGDEKMK7nYV3atT6FpEdg0RLeIfp19952V5xKW2IrL1XRBzw+yOIkoEmPWudF
         Ankf37hGVH1GuUr8lfvzfjo7IC5skvP+ktlsNmD1wC9Gkf6cW91SxgBN8FXOERIsFcMK
         At2ey8opxhAcerh5pQYkLdvN5LK6PntomsQ0AotX1Lgfs8XzhpJcUkgJrz7wpXoG6N6S
         wcXrzoBwzIse5lJnDwxODWO7dKFiPVvm6ODliY+DfuExF7d7wSRnWdQ+GQ6LwcQyqTJa
         7iPkkZmx2B8T8GQ2BIhjuovaFhBCJPQBa9YO9zVXJdSFLLapLVhuGdLBYmKsg7CqnMpP
         nzOQ==
X-Received: by 10.52.17.81 with SMTP id m17mr5710083vdd.18.1368810665728; Fri,
 17 May 2013 10:11:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.59.6.68 with HTTP; Fri, 17 May 2013 10:10:45 -0700 (PDT)
From: Rahul Bhattacharjee <rahul.rec.dgp@gmail.com>
Date: Fri, 17 May 2013 22:40:45 +0530
Message-ID: 
 <CAO7hTbPdMqNvrTY07ziuQ1oZHVdayf07ue282eP47Ti-kSWTTA@mail.gmail.com>
Subject: HDFS write failures!
To: "user@hadoop.apache.org" <user@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=bcaec5040c927ee2f004dced117d
X-Virus-Checked: Checked by ClamAV on apache.org

--bcaec5040c927ee2f004dced117d
Content-Type: text/plain; charset=UTF-8

Hi,

I was going through some documents about HDFS write pattern. It looks like
the write pipeline is closed when a error is encountered and the faulty
node is  taken out of the pipeline and the write continues.Few other
intermediate steps are to move the un-acked packets from ack queue to the
data queue.

My question is , is this faulty data node is reported to the NN and whether
NN would continue to use it as a valid DN while serving other write
requests in future or will it make it as faulty ?

Thanks,
Rahul

--bcaec5040c927ee2f004dced117d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:courier =
new,monospace;color:rgb(0,0,0)">Hi,<br><br></div><div class=3D"gmail_defaul=
t" style=3D"font-family:courier new,monospace;color:rgb(0,0,0)">I was going=
 through some documents about HDFS write pattern. It looks like the write p=
ipeline is closed when a error is encountered and the faulty node is=C2=A0 =
taken out of the pipeline and the write continues.Few other intermediate st=
eps are to move the un-acked packets from ack queue to the data queue.<br>

<br></div><div class=3D"gmail_default" style=3D"font-family:courier new,mon=
ospace;color:rgb(0,0,0)">My question is , is this faulty data node is repor=
ted to the NN and whether NN would continue to use it as a valid DN while s=
erving other write requests in future or will it make it as faulty ?<br>

<br></div><div class=3D"gmail_default" style=3D"font-family:courier new,mon=
ospace;color:rgb(0,0,0)">Thanks,<br>Rahul<br></div></div>

--bcaec5040c927ee2f004dced117d--