hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhe Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-10798) Make the threshold of reporting FSNamesystem lock contention configurable
Date Fri, 26 Aug 2016 02:20:20 GMT

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

Zhe Zhang updated HDFS-10798:
-----------------------------
    Description: Currently {{FSNamesystem#WRITELOCK_REPORTING_THRESHOLD}} is set at 1 second.
In a busy system a lower overhead might be desired. In other scenarios, more aggressive reporting
might be desired. We should make the threshold configurable.  (was: Currently {{FSNamesystem#WRITELOCK_REPORTING_THRESHOLD}}
is set at 1 second. In a busy system this might add too much overhead. We should make the
threshold configurable.)

> Make the threshold of reporting FSNamesystem lock contention configurable
> -------------------------------------------------------------------------
>
>                 Key: HDFS-10798
>                 URL: https://issues.apache.org/jira/browse/HDFS-10798
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: logging, namenode
>            Reporter: Zhe Zhang
>            Assignee: Erik Krogen
>              Labels: newbie
>         Attachments: HDFS-10789.001.patch
>
>
> Currently {{FSNamesystem#WRITELOCK_REPORTING_THRESHOLD}} is set at 1 second. In a busy
system a lower overhead might be desired. In other scenarios, more aggressive reporting might
be desired. We should make the threshold configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message