[
https://issues.apache.org/jira/browse/HDFS-17685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18028895#comment-18028895
]
ASF GitHub Bot commented on HDFS-17685:
---------------------------------------
github-actions[bot] commented on PR #7215:
URL: https://github.com/apache/hadoop/pull/7215#issuecomment-3387856322
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> Option to explicitly choose DFS client lease renewal interval
> -------------------------------------------------------------
>
> Key: HDFS-17685
> URL: https://issues.apache.org/jira/browse/HDFS-17685
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: dfsclient
> Reporter: Charles Connell
> Priority: Minor
> Labels: pull-request-available
>
> Currently, DFSClients send lease renewals to the NameNode at an interval
> equal to half of {{ipc.client.rpc-timeout.ms}}. This logic dates back to 2009
> in HDFS-278. At my company, we are interested in using short DFS client
> timeouts (< 10 seconds). However, we're currently hesitant to do so because
> that would flood the NameNode with lease renewals.
> I propose a setting {{dfs.client.lease.renewal.interval.ms}} that, if
> nonzero, would be used as the lease renewal interval instead of
> {{ipc.client.rpc-timeout.ms / 2}}. This would be useful for advanced users
> that want to control their RPC timeout and lease renewals separately.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
