[
https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992240#comment-16992240
]
zhuqi commented on HDFS-15041:
------------------------------
Hi [~hexiaoqiao]
Our one cluster with too many deleted operations and write operations because
of our new hive lifetime system with too many partitions . In some cases the
4ms will be too short to handle, so i want to let it to be configurable. Also
some presto based realtime situation without using read from standby, may want
to shorter the max lock time, in order to better the read performance.
Thanks.
> 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]
