[
https://issues.apache.org/jira/browse/HDFS-16703?focusedWorklogId=796623&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796623
]
ASF GitHub Bot logged work on HDFS-16703:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Jul/22 14:01
Start Date: 30/Jul/22 14:01
Worklog Time Spent: 10m
Work Description: slfan1989 commented on PR #4660:
URL: https://github.com/apache/hadoop/pull/4660#issuecomment-1200163090
> Thanks @slfan1989 for your explain.
>
> `ipc.client.rpc-timeout.ms` default is 2min. If client can‘t receive the
response within 2min, maybe we should give a high priority to improving the
performance of namenode.
>
> If timeout is 0, Client will be blocked for a very long time, such as
15min, due to NN crash or bad network or other reasons.
Thanks for the explanation, let's see what other partners think.
Thanks again for your contribution, let me learn something.
Issue Time Tracking
-------------------
Worklog Id: (was: 796623)
Time Spent: 1h 10m (was: 1h)
> 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: 1h 10m
> 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]
