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-1583) AlreadyBeingCreatedException because pendingCreates is non-null
Date Thu, 12 Jul 2007 19:47:04 GMT

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

dhruba borthakur updated HADOOP-1583:

    Priority: Major  (was: Blocker)

This is not a regression from earlier releases, so i am removing the "Blocker" tag.

> AlreadyBeingCreatedException because pendingCreates is non-null
> ---------------------------------------------------------------
>                 Key: HADOOP-1583
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1583
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.9.2
>            Reporter: Konstantin Shvachko
>             Fix For: 0.14.0
> When a client lease expires the lease monitor removes it from the  list of leases, but
> does not release pendingCreates files. When the name-node sees a file in pendingCreates
> which does not have a lease for the original client it throws AlreadyBeingCreatedException.
> This was reported in several issues like HADOOP-1411, but has never been resolved.
> I see two approaches:
> # clean pendingCreates when leases expire, or
> # reuse entries in pending creates for which there are no lease.
> The first is preferable imo since it cleans memory at the right time.

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

View raw message