[
https://issues.apache.org/jira/browse/HADOOP-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated HADOOP-726:
--------------------------------
Status: Open (was: Patch Available)
I think what's most important is to deprecate the public methods. You've
deprecated a number of package-private methods, and left some prominent public
methods, like FileSystem#lock(), S3FileSystem#lock() and
LocalFileSystem#lock(). These should also be deprecated. A separate issue
should be created that removes these methods and their implementations in the
next release.
> 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
> Attachments: HADOOP-726-1.patch, remove-fs-locks.patch
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
