[ 
https://issues.apache.org/jira/browse/HDFS-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042847#comment-17042847
 ] 

Hudson commented on HDFS-15041:
-------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17979 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/17979/])
HDFS-15041. Make MAX_LOCK_HOLD_MS and full queue size configurable. 
(ayushsaxena: rev 9eb7a8bdf8f3b1dc76efc22db9651474303d309e)
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml


> 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
>             Fix For: 3.3.0
>
>         Attachments: HDFS-15041.001.patch, HDFS-15041.002.patch, 
> HDFS-15041.003.patch, HDFS-15041.004.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]

Reply via email to