hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3176) Change lease record when a open-for-write-file gets renamed
Date Tue, 15 Apr 2008 19:09:05 GMT

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

dhruba borthakur updated HADOOP-3176:

    Attachment: danglingLease2.patch

1. Fixed findbugs warnings.
2. Enhanced test case by renaming a directory that has two open files in its subdirectory.
3. Removed LeaseComparator
4. All debug logs are encapsulated inside IsDebugEnabled()

> 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, danglingLease2.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.

View raw message