[
https://issues.apache.org/jira/browse/HDFS-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13854984#comment-13854984
]
Hudson commented on HDFS-5681:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #4924 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/4924/])
HDFS-5681. renewLease should not hold fsn write lock. Contributed by Daryn
Sharp. (kihwal:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1552711)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
> renewLease should not hold fsn write lock
> -----------------------------------------
>
> Key: HDFS-5681
> URL: https://issues.apache.org/jira/browse/HDFS-5681
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Fix For: 3.0.0, 2.4.0
>
> Attachments: HDFS-5681.patch
>
>
> Lease renewals unnecessarily hold the write lock which reduces throughput.
> Currently the fsn lock doubles as an "operational lock" to prevent state
> transitions. If the lease manager is thread-safe then a read lock is
> sufficient.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
