[
https://issues.apache.org/jira/browse/HDFS-11466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe Zhang updated HDFS-11466:
-----------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.8.1
3.0.0-alpha3
2.7.4
Status: Resolved (was: Patch Available)
+1; I just committed the patch to trunk, branch-2, branch-2.8, and branch-2.7.
Thanks Andrew for the fix.
> 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: [email protected]
For additional commands, e-mail: [email protected]
