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 "Ayush Saxena (Jira)" <ji...@apache.org> on 2020/02/22 20:50:00 UTC
[jira] [Commented] (HDFS-15041) Make MAX_LOCK_HOLD_MS and full
queue size configurable
[ https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042703#comment-17042703 ]
Ayush Saxena commented on HDFS-15041:
-------------------------------------
Thanx [~zhuqi] for the patch.
we can make the configuration support time units. and get the time using {{conf.getTimeDuration(..)}}
> Make MAX_LOCK_HOLD_MS and full queue size configurable
> ------------------------------------------------------
>
> Key: HDFS-15041
> URL: https://issues.apache.org/jira/browse/HDFS-15041
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Affects Versions: 3.2.0
> Reporter: zhuqi
> Assignee: zhuqi
> Priority: Major
> Attachments: HDFS-15041.001.patch, HDFS-15041.002.patch
>
>
> Now the MAX_LOCK_HOLD_MS and the full queue size are fixed. But different cluster have different need for the latency and the queue health standard. We'd better to make the two parameter configurable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org