[
https://issues.apache.org/jira/browse/HDFS-16703?focusedWorklogId=797446&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-797446
]
ASF GitHub Bot logged work on HDFS-16703:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Aug/22 23:47
Start Date: 02/Aug/22 23:47
Worklog Time Spent: 10m
Work Description: goiri commented on PR #4660:
URL: https://github.com/apache/hadoop/pull/4660#issuecomment-1203326152
I tend to agree that we should avoid not changing the previous behavior.
Can we add one setting that allows keeping the old 0 for the default case
and tune it for the rest?
Issue Time Tracking
-------------------
Worklog Id: (was: 797446)
Time Spent: 1.5h (was: 1h 20m)
> Enable RPC Timeout for some protocols of NameNode.
> --------------------------------------------------
>
> Key: HDFS-16703
> URL: https://issues.apache.org/jira/browse/HDFS-16703
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: ZanderXu
> Assignee: ZanderXu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> When I read some code about protocol, I found that only
> ClientNamenodeProtocolPB proxy with RPC timeout, other protocolPB proxy
> without RPC timeout, such as RefreshAuthorizationPolicyProtocolPB,
> RefreshUserMappingsProtocolPB, RefreshCallQueueProtocolPB,
> GetUserMappingsProtocolPB and NamenodeProtocolPB.
>
> If proxy without rpc timeout, it will be blocked for a long time if the NN
> machine crash or bad network during writing or reading with NN.
>
> So I feel that we should enable RPC timeout for all ProtocolPB.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
