hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11466) Change dfs.namenode.write-lock-reporting-threshold-ms default from 1000ms to 5000ms
Date Tue, 28 Feb 2017 17:33:45 GMT

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

Hudson commented on HDFS-11466:
-------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11319 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/11319/])
HDFS-11466. Change dfs.namenode.write-lock-reporting-threshold-ms (zhz: rev d269b488a71a158d3ddcbdea96992abe29725c69)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java


> 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
>             Fix For: 2.7.4, 3.0.0-alpha3, 2.8.1
>
>         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


Mime
View raw message