hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10798) Make the threshold of reporting FSNamesystem lock contention configurable
Date Tue, 28 Feb 2017 00:17:45 GMT

    [ https://issues.apache.org/jira/browse/HDFS-10798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886834#comment-15886834
] 

Andrew Wang commented on HDFS-10798:
------------------------------------

Thanks for the background Erik. I filed a simple patch on HDFS-11466 to bump this default
to 5000ms, we can continue the discussion there.

> 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
>             Fix For: 2.8.0, 2.7.4, 3.0.0-alpha1
>
>         Attachments: HDFS-10789.001.patch, HDFS-10789.002.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.15#6346)

---------------------------------------------------------------------
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