[
https://issues.apache.org/jira/browse/HDFS-17030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747783#comment-17747783
]
ASF GitHub Bot commented on HDFS-17030:
---------------------------------------
xinglin commented on PR #5878:
URL: https://github.com/apache/hadoop/pull/5878#issuecomment-1652970923
Hi @goiri,
I guess I will not continue submitting new builds. Tested these five failed
unit tests locally and some tests are flaky. Here are executions which
succeeded.
```
[INFO] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
219.328 s - in org.apache.hadoop.hdfs.TestReconstructStripedFileWithValidator
[INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
299.811 s - in org.apache.hadoop.hdfs.server.datanode.TestDirectoryScanner
[INFO] Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
193.482 s - in org.apache.hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA
[INFO] Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
428.261 s - in
org.apache.hadoop.hdfs.server.sps.TestExternalStoragePolicySatisfier
[INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
90.887 s - in org.apache.hadoop.hdfs.server.namenode.ha.TestHASafeMode
```
> Limit wait time for getHAServiceState in ObserverReaderProxy
> ------------------------------------------------------------
>
> Key: HDFS-17030
> URL: https://issues.apache.org/jira/browse/HDFS-17030
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Affects Versions: 3.4.0
> Reporter: Xing Lin
> Assignee: Xing Lin
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.4.0
>
>
> When namenode HA is enabled and a standby NN is not responsible, we have
> observed it would take a long time to serve a request, even though we have a
> healthy observer or active NN.
> Basically, when a standby is down, the RPC client would (re)try to create
> socket connection to that standby for _ipc.client.connect.timeout_ _*
> ipc.client.connect.max.retries.on.timeouts_ before giving up. When we take a
> heap dump at a standby, the NN still accepts the socket connection but it
> won't send responses to these RPC requests and we would timeout after
> _ipc.client.rpc-timeout.ms._ This adds a significantly latency. For clusters
> at Linkedin, we set _ipc.client.rpc-timeout.ms_ to 120 seconds and thus a
> request takes more than 2 mins to complete when we take a heap dump at a
> standby. This has been causing user job failures.
> We could set _ipc.client.rpc-timeout.ms to_ a smaller value when sending
> getHAServiceState requests in ObserverReaderProxy (for user rpc requests, we
> still use the original value from the config). However, that would double the
> socket connection between clients and the NN (which is a deal-breaker).
> The proposal is to add a timeout on getHAServiceState() calls in
> ObserverReaderProxy and we will only wait for the timeout for an NN to
> respond its HA state. Once we pass that timeout, we will move on to probe the
> next NN.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
