hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7059) HAadmin transtionToActive with forceActive option can show confusing message.
Date Tue, 16 Sep 2014 18:40:36 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135932#comment-14135932
] 

Hudson commented on HDFS-7059:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #1898 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1898/])
HDFS-7059. HAadmin transtionToActive with forceActive option can show (kihwal: rev 2f847b3357448184aaec935052f34d116ad3a42c)
* hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/tools/TestDFSHAAdminMiniCluster.java
* hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ha/HAAdmin.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt


> 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: Improvement
>    Affects Versions: 2.0.0-alpha, 3.0.0
>            Reporter: Rushabh S Shah
>            Assignee: Rushabh S Shah
>            Priority: Minor
>             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)

Mime
View raw message