hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5239) Allow FSNamesystem lock fairness to be configurable
Date Tue, 15 Oct 2013 17:54:43 GMT

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

Daryn Sharp updated HDFS-5239:
------------------------------

    Attachment: HADOOP-5239.branach-23.patch

Port to 23, will of course fail pre-commit.

> 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: HADOOP-5239.branach-23.patch, 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message