Return-Path: 
 <user-return-15786-apmail-hadoop-common-user-archive=hadoop.apache.org@hadoop.apache.org>
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 CB5D811C19
	for <apmail-hadoop-common-user-archive@www.apache.org>;
 Mon, 16 Jun 2014 15:26:38 +0000 (UTC)
Received: (qmail 38072 invoked by uid 500); 16 Jun 2014 15:26:29 -0000
Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org
Received: (qmail 37946 invoked by uid 500); 16 Jun 2014 15:26:29 -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 37936 invoked by uid 99); 16 Jun 2014 15:26:28 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jun 2014 15:26:28 +0000
X-ASF-Spam-Status: No, hits=2.1 required=5.0
	tests=HK_RANDOM_ENVFROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of lrdbgy@gmail.com designates
 209.85.219.47 as permitted sender)
Received: from [209.85.219.47] (HELO mail-oa0-f47.google.com) (209.85.219.47)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jun 2014 15:26:25 +0000
Received: by mail-oa0-f47.google.com with SMTP id n16so6025576oag.6
        for <user@hadoop.apache.org>; Mon, 16 Jun 2014 08:26:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:date:message-id:subject:from:to:content-type;
        bh=CxJjCwMw0LYWJmmsbMR3Kg4rDEQaFNiaGMHrSAZ439Q=;
        b=X+tWXeAtxYqt2fMtH5/ShOFC7LT8+T/xvVMqntqT2+QnqN5mrArrb1ZTq6+BoaeSKX
         LEENvi9DxRt4CIJKdRC2zprMlkKHjj/Bx14c8LCitfvuIxw2yRuF7LyeSjU8VtLpyjao
         FKkNEE3bUYRtYZswdBWeP9SSswDFwEgCEyMlLjNxzZot3IaH8dTqtNe1phxcwJ2chY90
         LAZ91Inf7YcuxC61pQu/dMz08HJXuTf+2D1OkM9sndAXaBLcjqhT3lufdApC4DIG4HYF
         7J3ziBL5gGZEnck+vXXUzDieyWr9nQesee/BH05vhSkk/I1XirgLq6bqUKDj0iojBpfl
         8bMg==
MIME-Version: 1.0
X-Received: by 10.182.78.8 with SMTP id x8mr3583190obw.61.1402932361316; Mon,
 16 Jun 2014 08:26:01 -0700 (PDT)
Sender: lrdbgy@gmail.com
Received: by 10.60.80.1 with HTTP; Mon, 16 Jun 2014 08:26:01 -0700 (PDT)
Date: Mon, 16 Jun 2014 17:26:01 +0200
X-Google-Sender-Auth: zYqQ4SFidrX6-vFY8Nmjo3dDbPM
Message-ID: 
 <CALgX=ZG9sJNiwRrdiB3Kdv4FQpyU5b5v+WWV_W=+x+rSU7q_pw@mail.gmail.com>
Subject: Recover HDFS lease after crash
From: Anonymous <lrdbgy+hdfs@gmail.com>
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=047d7b2e44b60a502604fbf5a5b5
X-Virus-Checked: Checked by ClamAV on apache.org

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

Hello,

I have a long running application that opens a file and periodically
appends to it. If this application is killed and then restarted it cannot
open the same file again for some time (~ 1minute). First, it gets the
AlreadyBeingCreated exception (which I guess means namenode doesn't yet
know the program crashed) and then the RecoveryInProgress exception (which
I guess means the namenode proceeded to close and release the file after
inactivity). After about 1 minute it starts to work again.

What is the correct way to recover from this? Is there API for recovering
the lease and resuming appending faster? DFSClient sets a randomized client
name. If it were to send the same client name as before the crash, would it
receive a lease on the file faster?

Thanks

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

<div dir=3D"ltr">Hello,<div><br></div><div><div>I have a long running appli=
cation that opens a file and periodically appends to it. If this applicatio=
n is killed and then restarted it cannot open the same file again for some =
time (~ 1minute). First, it gets the AlreadyBeingCreated exception (which I=
 guess means namenode doesn&#39;t yet know the program crashed) and then th=
e RecoveryInProgress exception (which I guess means the namenode proceeded =
to close and release the file after inactivity). After about 1 minute it st=
arts to work again.</div>
<div><br></div><div>What is the correct way to recover from this? Is there =
API for recovering the lease and resuming appending faster? DFSClient sets =
a randomized client name. If it were to send the same client name as before=
 the crash, would it receive a lease on the file faster?</div>
</div><div><br></div><div>Thanks</div></div>

--047d7b2e44b60a502604fbf5a5b5--