[
https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991983#comment-16991983
]
Wei-Chiu Chuang commented on HDFS-15041:
----------------------------------------
[~hexiaoqiao] does it make sense to make MAX_LOCK_HOLD_MS configurable after
your change in HDFS-14553?
Also, let's understand the use case better: if the purpose is to make balancer
not to overwhelm NameNode, there are other solutions that look even more
promising, such as HDFS-13183, or HDFS-14162 (if consistent read from standby
is enabled).
> 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
> Priority: Major
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
