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/20 01:10:30 UTC

[jira] Assigned: (HADOOP-726) HDFS locking mechanisms should be simplified or removed

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

Raghu Angadi reassigned HADOOP-726:
-----------------------------------

    Assignee: Raghu Angadi  (was: Sameer Paranjpye)

> HDFS locking mechanisms should be simplified or removed
> -------------------------------------------------------
>
>                 Key: HADOOP-726
>                 URL: https://issues.apache.org/jira/browse/HADOOP-726
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Sameer Paranjpye
>         Assigned To: Raghu Angadi
>            Priority: Minor
>
> HDFS includes a locking mechanism that allows clients to lock files and directories in the filesystem. This requires that the Namenode, in addition to all other management of filesystem state also has to act like a lock manager on behalf of clients. Rather than burden the Namenode with this Hadoop should include a distinct general purpose distributed lock manager.
> In the interim, the locking functionality on the filesystem should be simplified to permit only file locks or removed altogether. At this point, removing or simplifying the functionality is not likely to break client code, removing it later will be much harder. In any case, locks in HDFS don't work very well, see HADOOP-656. Also, directory locks are overkill most UNIX fses don't support it.

-- 
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