[
https://issues.apache.org/jira/browse/HDFS-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee updated HDFS-7059:
-----------------------------
Resolution: Fixed
Fix Version/s: 2.6.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
> HAadmin transtionToActive with forceActive option can show confusing message.
> -----------------------------------------------------------------------------
>
> Key: HDFS-7059
> URL: https://issues.apache.org/jira/browse/HDFS-7059
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Rushabh S Shah
> Assignee: Rushabh S Shah
> Fix For: 2.6.0
>
> Attachments: HDFS-7059.patch
>
>
> Ran into this confusing message on our local HA setup.
> One of the namenode was down and the other was in standby mode.
> The namenode was not able to come out of safe mode so we did
> transitionToActive with forceActive switch enabled.
> Due to change in HDFS-2949, it will try connecting to all the namenode to
> see whether they are active or not.
> But since the other namenode is down it will try connect to that namenode for
> 'ipc.client.connect.max.retries' number of times.
> Every time it is not able to connect, it will log a message :
> INFO ipc.Client: Retrying connect to server: <server name>. Already tried 0
> time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=50,
> sleepTime=1000 MILLISECONDS)
> Since in our configuration, the number of retries is 50, it will show this
> message 50 times.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
