hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (HADOOP-656) dfs locking doesn't notify the application when a lock is lost
Date Fri, 05 Jan 2007 00:27:28 GMT

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

Raghu Angadi reassigned HADOOP-656:

    Assignee: Sameer Paranjpye  (was: Raghu Angadi)

These locks are expected to be moved out of DFS in near future.

> 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
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.7.2
>            Reporter: Owen O'Malley
>         Assigned To: 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.
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message