Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <6490646.1184269624658.JavaMail.jira@brutus>
Date: Thu, 12 Jul 2007 12:47:04 -0700 (PDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-1583) AlreadyBeingCreatedException because
 pendingCreates is non-null
In-Reply-To: <11171727.1184049844438.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-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.