[
https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992223#comment-16992223
]
Xiaoqiao He commented on HDFS-15041:
------------------------------------
Thanks [~weichiu] for your invite. In my experience, 4 ms by default is
suitable for me and not meet issues anymore, since this acts for RPC request
#blockReceivedAndDeleted only. I also wonder the purposes why to tune this
parameters. Some cases meet will be better to decide whether it is need. FYI.
Thanks again.
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
