hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7059) HAadmin transtionToActive with forceActive option can show confusing message.
Date Fri, 12 Sep 2014 23:21:34 GMT

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

Hadoop QA commented on HDFS-7059:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision 957414d.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-common-project/hadoop-common


                                      The test build failed in hadoop-hdfs-project/hadoop-hdfs

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/8010//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8010//console

This message is automatically generated.

> 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
>         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

This message was sent by Atlassian JIRA

View raw message