Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 26 Jan 2017 19:03:24 +0000 (UTC)
From: "Vivek Rathod (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13038228.1485457396000.5639.1485457404341@Atlassian.JIRA>
In-Reply-To: <JIRA.13038228.1485457396000@Atlassian.JIRA>
References: <JIRA.13038228.1485457396000@Atlassian.JIRA> <JIRA.13038228.1485457396108@jira-lw-us.apache.org>
Subject: [jira] [Created] (AMBARI-19730) Namenodes fail to come up after
 removing some Journalnodes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 26 Jan 2017 19:03:32 -0000

Vivek Rathod created AMBARI-19730:
-------------------------------------

             Summary: Namenodes fail to come up after removing some Journalnodes
                 Key: AMBARI-19730
                 URL: https://issues.apache.org/jira/browse/AMBARI-19730
             Project: Ambari
          Issue Type: Bug
    Affects Versions: 2.5.0
            Reporter: Vivek Rathod
             Fix For: 2.5.0


Namenodes fail to come up after removing some Journalnodes
STR:
Deploy a 6 node HA cluster using Blueprints, with 6 Journalnodes. 
Remove 2 Journalnodes using Manage JN Wizard
In the Start All Services in Manage JN Wizard, Both the Namenodes fail to come up.

{code}
17/01/26 03:39:56 INFO ipc.Client: Retrying connect to server: <INTERNAL_HOST_NAME>/<EXTERNAL_HOST_NAME>:8020. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=1, sleepTime=1000 MILLISECONDS)
17/01/26 03:39:56 WARN ipc.Client: Failed to connect to server: <INTERNAL_HOST_NAME>/<EXTERNAL_HOST_NAME>:8020: retries get failed due to exceeded maximum allowed retries number: 1
java.net.ConnectException: Connection refused
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
	at org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
	at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
	at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
	at org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
	at org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
	at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
	at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
	at org.apache.hadoop.ipc.Client.call(Client.java:1449)
	at org.apache.hadoop.ipc.Client.call(Client.java:1396)
	at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
	at com.sun.proxy.$Proxy8.getServiceStatus(Unknown Source)
	at org.apache.hadoop.ha.protocolPB.HAServiceProtocolClientSideTranslatorPB.getServiceStatus(HAServiceProtocolClientSideTranslatorPB.java:122)
	at org.apache.hadoop.ha.HAAdmin.getServiceState(HAAdmin.java:359)
	at org.apache.hadoop.ha.HAAdmin.runCmd(HAAdmin.java:457)
	at org.apache.hadoop.hdfs.tools.DFSHAAdmin.runCmd(DFSHAAdmin.java:120)
	at org.apache.hadoop.ha.HAAdmin.run(HAAdmin.java:384)
	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
	at org.apache.hadoop.hdfs.tools.DFSHAAdmin.main(DFSHAAdmin.java:132)
{code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)