hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (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 01:15:45 GMT

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

Junping Du commented on HDFS-11466:
-----------------------------------

Thanks [~andrew.wang] for pinging me on this. Yes. 2.8.0 is pending on HADOOP-13866 decision
which should get resolved soon. About patch here, if it is really important (seems unlikely
at first glance), we can get it to 2.8.0. Otherwise, my suggestion is better to leave it to
2.8.1.

> 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


Mime
View raw message