[
https://issues.apache.org/jira/browse/HDFS-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776282#comment-13776282
]
Hudson commented on HDFS-5239:
------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1558 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1558/])
HDFS-5239. Allow FSNamesystem lock fairness to be configurable (daryn) (daryn:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1525624)
* /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
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSNamesystem.java
> Allow FSNamesystem lock fairness to be configurable
> ---------------------------------------------------
>
> Key: HDFS-5239
> URL: https://issues.apache.org/jira/browse/HDFS-5239
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Fix For: 3.0.0, 2.3.0
>
> Attachments: HDFS-5239.patch
>
>
> The fairness of the {{FSNamesystem#fsLock}} is hardcoded to {{true}}. Using
> an unfair lock provides a negligible increase to throughput. However this is
> due to bottlenecks elsewhere in the system. In combination with other
> changes, such as RPC layer and audit logging, preliminary tests show up to a
> 5X improvement for a read heavy workload.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
