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-11466) Change dfs.namenode.write-lock-reporting-threshold-ms default from 1000ms to 5000ms
Date Tue, 28 Feb 2017 01:05:45 GMT

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

Andrew Wang commented on HDFS-11466:

Hi Zhe, so far it hasn't been released, though 2.8.0 is close to release. I think there's
still time to sneak in this simple change if you think it's important to get this done before
it gets released, though I don't consider this change incompatible.

Ping [~djp] for awareness.

> 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

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

View raw message