Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Sun, 14 Jun 2015 04:58:01 +0000 (UTC)
From: "Jaimin D Jetly (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12837618.1434223391000.66115.1434257881182@Atlassian.JIRA>
In-Reply-To: <JIRA.12837618.1434223391000@Atlassian.JIRA>
References: <JIRA.12837618.1434223391000@Atlassian.JIRA>
 <JIRA.12837618.1434223391292@arcas>
Subject: [jira] [Commented] (AMBARI-11908) ResourceManager fails initial
 start when not colocated with Namenode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jaimin D Jetly commented on AMBARI-11908:
-----------------------------------------

[~miharp]
The task log as shown in the description has following error message 
{code}
Fail: Execution of 'curl -s 'http://helios1.labs.teradata.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus'' returned 7. 
{code}
Curl error code "7"  stands for *curl failing to connect*.

Do you know any obvious reason why host with RM2 was not able to connect to helios1.labs.teradata.com host? 
It could be something like firewall selinux, namenode process was in INSTALLED state and so not running, namenode host is getting rebooted, etc


> ResourceManager fails initial start when not colocated with Namenode
> --------------------------------------------------------------------
>
>                 Key: AMBARI-11908
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11908
>             Project: Ambari
>          Issue Type: Bug
>         Environment: sles11sp3
> hdp-2.3.0.0-2346
> ambari-2.1.0-1064
>            Reporter: Michael Harp
>             Fix For: 2.1.0
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Deploying with blueprint and Namenode-HA and Yarn-HA enabled resoucemanager fails initial start. Subsequent starts succeed.
> {code}
> 2015-06-13 03:41:24,922 - Getting jmx metrics from NN failed. URL: http://helios1.labs.teradata.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py", line 37, in get_value_from_jmx
>     _, data = shell.checked_call(cmd, user=run_user, quiet=False)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 70, in inner
>     result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 92, in checked_call
>     tries=tries, try_sleep=try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 140, in _call_wrapper
>     result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 282, in _call
>     raise Fail(err_msg)
> Fail: Execution of 'curl -s 'http://helios1.labs.teradata.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus'' returned 7. 
> 2015-06-13 03:41:25,000 - Getting jmx metrics from NN failed. URL: http://helios2.labs.teradata.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
> {code}


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