You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2007/01/04 22:17:27 UTC
[jira] Assigned: (HADOOP-656) dfs locking doesn't notify the
application when a lock is lost
[ https://issues.apache.org/jira/browse/HADOOP-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghu Angadi reassigned HADOOP-656:
-----------------------------------
Assignee: Raghu Angadi (was: Sameer Paranjpye)
> 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: Raghu Angadi
>
> 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