[
https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992124#comment-16992124
]
zhuqi edited comment on HDFS-15041 at 12/10/19 5:48 AM:
--------------------------------------------------------
Hi [~weichiu]
Yeah, i mean to make MAX_LOCK_HOLD_MS configurable after my change in
HDFS-14553, because of the different need for client latency and balance the
pressure for rpc queue. Sorry for the mistake , not mean the hdfs balancer, the
balancer pressure i have changed to standby.
was (Author: zhuqi):
Hi [~weichiu]
Yeah, i mean to make MAX_LOCK_HOLD_MS configurable after my change in
HDFS-14553, because of the different need for client latency and balance the
pressure for rpc queue. Sorry for the mistake , not mean the hdfs balancer, the
balancer pressure i have changed to standby. Also we can add this queue size
to metrics if needed?
> 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
> Attachments: HDFS-15041.001.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: [email protected]
For additional commands, e-mail: [email protected]
