[
https://issues.apache.org/jira/browse/HDFS-17685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17987159#comment-17987159
]
Nishtha Shah edited comment on HDFS-17685 at 7/1/25 9:31 AM:
-------------------------------------------------------------
[~charlesconnell] [~ndimiduk] [~zeekling]
Just checking if there’s any update on the plan to merge this. Wondering if
it's likely to land soon or if there's anything still under discussion.
Appreciate any insights
cc [~apurtell]
was (Author: nishtha11shah):
[~charlesconnell] [~ndimiduk] [~zeekling]
Just checking if there’s any update on the plan to merge this. Wondering if
it's likely to land soon or if there's anything still under discussion.
Appreciate any insights
> 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]
