Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <24794583.1208071504883.JavaMail.jira@brutus>
Date: Sun, 13 Apr 2008 00:25:04 -0700 (PDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-3176) Change lease record when a
 open-for-write-file gets renamed
In-Reply-To: <265539455.1207341684390.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

dhruba borthakur updated HADOOP-3176:
-------------------------------------

    Status: Patch Available  (was: Open)

> Change lease record when a open-for-write-file gets renamed
> -----------------------------------------------------------
>
>                 Key: HADOOP-3176
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3176
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: danglingLease.patch
>
>
> When a file/directory is removed, the namenode should repair the leases so that the existing leases point to the  appropriate file. The lease record has the pathname of the file that it refers to.
> This is required because the namenode has to invoke lease-recovery on the correct file if the client that was writing to a file dies.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.