Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <2028983717.1221586244423.JavaMail.jira@brutus>
Date: Tue, 16 Sep 2008 10:30:44 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Reopened: (HADOOP-656) dfs locking doesn't notify the
 application when a lock is lost
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Doug Cutting reopened HADOOP-656:
---------------------------------


Shouldn't have been resolved as "fixed".

> dfs locking doesn't notify the application when a lock is lost
> --------------------------------------------------------------
>
>                 Key: HADOOP-656
>                 URL: https://issues.apache.org/jira/browse/HADOOP-656
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.7.2
>            Reporter: Owen O'Malley
>            Assignee: Sameer Paranjpye
>
> DFS locks may be lost for failing to renew the lease on time, but the application is not notified about the loss of the lock and may therefore perform operations assuming it has the lock, even though the lock has been given to another process. I propose that DFS operations check to see if that client has lost a lock since the last check and if so throw a LostLockException.

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