You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Zhe Zhang (JIRA)" <ji...@apache.org> on 2017/02/28 01:01:44 UTC

[jira] [Commented] (HDFS-11466) Change dfs.namenode.write-lock-reporting-threshold-ms default from 1000ms to 5000ms

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

Zhe Zhang commented on HDFS-11466:
----------------------------------

Thanks for the patch Andrew. Quick question, did you check that the old default has not been included in any releases?

> Change dfs.namenode.write-lock-reporting-threshold-ms default from 1000ms to 5000ms
> -----------------------------------------------------------------------------------
>
>                 Key: HDFS-11466
>                 URL: https://issues.apache.org/jira/browse/HDFS-11466
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 2.8.0, 2.7.4, 3.0.0-alpha1
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>         Attachments: HDFS-11466.001.patch
>
>
> Per discussion on HDFS-10798, it might make sense to change the default value for long write lock holds to 5000ms like the read threshold, to avoid spamming the log.



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