[
https://issues.apache.org/jira/browse/HDFS-17918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDFS-17918:
----------------------------------
Labels: pull-request-available (was: )
> WebHDFS client-side failover fails during NameNode fsimage loading in HA
> ------------------------------------------------------------------------
>
> Key: HDFS-17918
> URL: https://issues.apache.org/jira/browse/HDFS-17918
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: KWON BYUNGCHANG
> Priority: Major
> Labels: pull-request-available
>
> When NameNode is configured with HA and NameNode 1 is restarting and loading
> fsimage, accessing WebHDFS does not trigger client-side failover.
> During fsimage loading after NameNode restart in HA configuration, WebHDFS
> returns RetriableException instead of StandbyException. Because of this, the
> client-side failover does not work and the client keeps retrying the same
> NameNode. Eventually the client fails because it cannot find the active
> NameNode.
>
> {noformat}
> $ hdfs dfs -ls swebhdfs://blue
> 2023-07-14 12:23:55,890 INFO web.WebHdfsFileSystem: Retrying connect to
> namenode: blue-nn1.host/10.10.10.10:9470. Already retried 0 time(s); retry
> policy is
> org.apache.hadoop.io.retry.RetryPolicies$FailoverOnNetworkExceptionRetry@95e33cc,
> delay 0ms.
> 2023-07-14 12:23:55,929 INFO web.WebHdfsFileSystem: Retrying connect to
> namenode: blue-nn1.host/10.10.10.10:9470. Already retried 1 time(s); retry
> policy is
> org.apache.hadoop.io.retry.RetryPolicies$FailoverOnNetworkExceptionRetry@95e33cc,
> delay 731ms.
> 2023-07-14 12:23:56,697 INFO web.WebHdfsFileSystem: Retrying connect to
> namenode: blue-nn1.host/10.10.10.10:9470. Already retried 2 time(s); retry
> policy is
> org.apache.hadoop.io.retry.RetryPolicies$FailoverOnNetworkExceptionRetry@95e33cc,
> delay 1475ms.
> 2023-07-14 12:23:58,207 INFO web.WebHdfsFileSystem: Retrying connect to
> namenode: blue-nn1.host/10.10.10.10:9470. Already retried 3 time(s); retry
> policy is
> org.apache.hadoop.io.retry.RetryPolicies$FailoverOnNetworkExceptionRetry@95e33cc,
> delay 5061ms.
> 2023-07-14 12:24:03,304 INFO web.WebHdfsFileSystem: Retrying connect to
> namenode: blue-nn1.host/10.10.10.10:9470. Already retried 4 time(s); retry
> policy is
> org.apache.hadoop.io.retry.RetryPolicies$FailoverOnNetworkExceptionRetry@95e33cc,
> delay 7898ms.
> 2023-07-14 12:24:11,235 INFO web.WebHdfsFileSystem: Retrying connect to
> namenode: blue-nn1.host/10.10.10.10:9470. Already retried 5 time(s); retry
> policy is
> org.apache.hadoop.io.retry.RetryPolicies$FailoverOnNetworkExceptionRetry@95e33cc,
> delay 18847ms.
> 2023-07-14 12:24:30,117 INFO web.WebHdfsFileSystem: Retrying connect to
> namenode: blue-nn1.host/10.10.10.10:9470. Already retried 6 time(s); retry
> policy is
> org.apache.hadoop.io.retry.RetryPolicies$FailoverOnNetworkExceptionRetry@95e33cc,
> delay 20826ms.
> 2023-07-14 12:24:50,979 INFO web.WebHdfsFileSystem: Retrying connect to
> namenode: blue-nn1.host/10.10.10.10:9470. Already retried 7 time(s); retry
> policy is
> org.apache.hadoop.io.retry.RetryPolicies$FailoverOnNetworkExceptionRetry@95e33cc,
> delay 10374ms.
> 2023-07-14 12:25:01,385 INFO web.WebHdfsFileSystem: Retrying connect to
> namenode: blue-nn1.host/10.10.10.10:9470. Already retried 8 time(s); retry
> policy is
> org.apache.hadoop.io.retry.RetryPolicies$FailoverOnNetworkExceptionRetry@95e33cc,
> delay 16640ms.
> 2023-07-14 12:25:18,059 INFO web.WebHdfsFileSystem: Retrying connect to
> namenode: blue-nn1.host/10.10.10.10:9470. Already retried 9 time(s); retry
> policy is
> org.apache.hadoop.io.retry.RetryPolicies$FailoverOnNetworkExceptionRetry@95e33cc,
> delay 15514ms.
> 2023-07-14 12:25:33,610 INFO web.WebHdfsFileSystem: Retrying connect to
> namenode: blue-nn1.host/10.10.10.10:9470. Already retried 10 time(s); retry
> policy is
> org.apache.hadoop.io.retry.RetryPolicies$FailoverOnNetworkExceptionRetry@95e33cc,
> delay 10745ms.
> ls: Namenode is in startup mode
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
