[
https://issues.apache.org/jira/browse/HDFS-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707225#comment-14707225
]
Ravi Prakash commented on HDFS-6697:
------------------------------------
And just to clarify [~wheat9]'s concern
https://issues.apache.org/jira/browse/HDFS-8344?focusedCommentId=14634172&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14634172
bq. I'm concerned with the complexity associated with the commit as well as the
difficulty for the users to choose the right configuration. It's an internal
implementation detail and it should not be exposed to users whenever it's
possible. We intentionally keep the soft and hard limit not configurable to
avoid the users shooting their foot.
That could be said for a lot of existing configuration, so I am not sure I buy
the argument. But I just thought of chiming in here to help us all make an
informed decision.
> Make NN lease soft and hard limits configurable
> -----------------------------------------------
>
> Key: HDFS-6697
> URL: https://issues.apache.org/jira/browse/HDFS-6697
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Ming Ma
> Assignee: J.Andreina
> Attachments: HDFS-6697.1.patch, HDFS-6697.2.patch, HDFS-6697.3.patch
>
>
> For testing, NameNodeAdapter allows test code to specify lease soft and hard
> limit via setLeasePeriod directly on LeaseManager. But NamenodeProxies.java
> still use the default values.
>
> It is useful if we can make NN lease soft and hard limit configurable via
> Configuration. That will allow NamenodeProxies.java to use the configured
> values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
