[
https://issues.apache.org/jira/browse/AMBARI-14782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118252#comment-15118252
]
Michael Harp commented on AMBARI-14782:
---------------------------------------
This is same workaround we used for
https://issues.apache.org/jira/browse/AMBARI-13693.
We had similar discussion at the time on whether using the optional Yarn HA
properties made sense or not.
Its a simple fix to update our blueprints to include these properties by
default but always more difficult to handle upgrades.
For the record this is our current workaround;
{code}
rm1=$(/var/lib/ambari-server/resources/scripts/configs.sh -port $AMBARI_PORT
get $MASTER1 $CLUSTERNAME yarn-site|grep yarn.resourcemanager.hostname.rm1|cut
-d ":" -f2|tr -d '"'|tr -d ','|tr -d ' ')
rm2=$(/var/lib/ambari-server/resources/scripts/configs.sh -port $AMBARI_PORT
get $MASTER1 $CLUSTERNAME yarn-site|grep yarn.resourcemanager.hostname.rm2|cut
-d ":" -f2|tr -d '"'|tr -d ','|tr -d ' ')
/var/lib/ambari-server/resources/scripts/configs.sh -port $AMBARI_PORT set
$MASTER1 $CLUSTERNAME yarn-site "yarn.resourcemanager.webapp.address.rm1"
"${rm1}:8088"
/var/lib/ambari-server/resources/scripts/configs.sh -port $AMBARI_PORT set
$MASTER1 $CLUSTERNAME yarn-site "yarn.resourcemanager.webapp.address.rm2"
"${rm2}:8088"
/var/lib/ambari-server/resources/scripts/configs.sh -port $AMBARI_PORT set
$MASTER1 $CLUSTERNAME yarn-site "yarn.resourcemanager.webapp.https.address.rm1"
"${rm1}:8090"
/var/lib/ambari-server/resources/scripts/configs.sh -port $AMBARI_PORT set
$MASTER1 $CLUSTERNAME yarn-site "yarn.resourcemanager.webapp.https.address.rm2"
"${rm2}:8090"
{code}
> 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.2
>
>
> 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)
