ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaimin Jetly (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21156) Yarn service check failure after moving resource manager to a different host - on wire encrypted cluster
Date Fri, 02 Jun 2017 17:55:04 GMT

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

Jaimin Jetly commented on AMBARI-21156:
---------------------------------------

+1 for the patch

> Yarn service check failure after moving resource manager to a different host - on wire
encrypted cluster
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21156
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21156
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.1
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>            Priority: Critical
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21156.patch
>
>
> Yarn service check is failing after moving the resource manager to a new host. This issue
is occuring only on wire encrypted cluster. I performed the same operation on non wire encrypted
cluster and service check is working fine.
> Steps to reproduce :
> 1) Move resource manager to a new host.
> 2) Run the service check.
> 3) Service check is failing with below exception :
> {code}
> Traceback (most recent call last):
>   File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py",
line 181, in <module>
>     ServiceCheck().execute()
>   File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 329, in execute
>     method(env)
>   File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py",
line 131, in service_check
>     active_rm_webapp_address = self.get_active_rm_webapp_address()
>   File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py",
line 177, in get_active_rm_webapp_address
>     raise Fail('Resource Manager state is not available. Failed to determine the active
Resource Manager web application address from {0}'.format(','.join(rm_webapp_addresses)));
> resource_management.core.exceptions.Fail: Resource Manager state is not available. Failed
to determine the active Resource Manager web application address from ctr-e133-1493418528701-64577-01-000002.hwx.site:8090
> {code}
> Even after moving the resource manager to new host,  its still referring to the older
resource manager host.
> *Workaround* : Property 'yarn.resourcemanager.webapp.https.address' was still referring
to older resource manager host. I have manually updated this property to new host and restarted
yarn. After this service check is going through fine.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message