[
https://issues.apache.org/jira/browse/AMBARI-14782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117534#comment-15117534
]
Robert Nettleton commented on AMBARI-14782:
-------------------------------------------
It looks like a recent change to the Yarn Service check scripts, AMBARI-14686,
is causing this to occur now.
The changes in AMBARI-14686 appear to be correct, in that the special handling
added to properly construct the URL to the RM instances seems like the correct
way to perform the Service Check in an HA environment.
h2. Workaround
Updating the "yarn-site" configuration in the Blueprint or Cluster Creation
template to include these properties in non-secure mode:
{code}
"yarn.resourcemanager.webapp.address.rm1" : "%HOSTGROUP::host_group_2%:8088",
"yarn.resourcemanager.webapp.address.rm2" : "%HOSTGROUP::host_group_3%:8088",
{code}
Or these properties in a secure setting:
{code}
"yarn.resourcemanager.webapp.https.address.rm1" :
"%HOSTGROUP::host_group_2%:8088",
"yarn.resourcemanager.webapp.https.address.rm2" :
"%HOSTGROUP::host_group_3%:8088",
{code}
should allow the service check to complete successfully.
Note: The actual property values may differ in a cluster deployment, depending
upon the host group names and ports used.
> Yarn service check fails with Blueprint deployed Yarn HA
> --------------------------------------------------------
>
> Key: AMBARI-14782
> URL: https://issues.apache.org/jira/browse/AMBARI-14782
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.2.1
> Environment: sles11sp3
> branch-2.2 | aacc16dd2cfb0f2b57c82fe214d9557327ec86bf
> Reporter: Michael Harp
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.2.1
>
>
> STR:
> # Deploy cluster using blueprint with [yarn ha
> enabled|https://cwiki.apache.org/confluence/display/AMBARI/Blueprint+Support+for+HA+Clusters#BlueprintSupportforHAClusters-BlueprintExample:YarnResourceManagerHACluster]
> # Run Yarn service check.
> {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 142, in <module>
> ServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py",
> line 118, in service_check
> info_app_url = params.scheme + "://" + rm_webapp_address +
> "/ws/v1/cluster/apps/" + application_name
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 81, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'yarn.resourcemanager.webapp.address.rm1' was not found in configurations
> dictionary!
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
