[
https://issues.apache.org/jira/browse/AMBARI-7738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179186#comment-14179186
]
Hadoop QA commented on AMBARI-7738:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12676154/AMBARI-7738.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/291//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/291//console
This message is automatically generated.
> Blueprints: Cluster deployment attempt in HDP 2.1 fails without Yarn
> APP_TIMELINE_SERVER
> ----------------------------------------------------------------------------------------
>
> Key: AMBARI-7738
> URL: https://issues.apache.org/jira/browse/AMBARI-7738
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 1.7.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Fix For: 1.7.0
>
> Attachments: AMBARI-7738.patch, AMBARI-7738_1.7.0.patch,
> blueprint.json, cluster.json
>
>
> When a user attempts to create an HDP 2.1 cluster based on a Blueprint that
> does not contain the following service:
> APP_TIMELINE_SERVER
> The cluster deployment will fail during the configuration step, and the
> following error will be sent back to the REST client:
> "{
> "status" : 400,
> "message" : "Unable to update configuration property with topology
> information. Component 'APP_TIMELINE_SERVER' is not mapped to any host group
> or is mapped to multiple groups."
> }"
> The Blueprint configuration processor currently includes a statically-defined
> list of properties that are candidates for topology updates. This basically
> means that the correct host information is added to these configuration
> properties when the cluster deployment is being prepared.
> Some recent changes to the Ambari trunk have included some Yarn configuration
> properties that are related to the Yarn Application Timeline Service (or ATS
> for short).
> The HDP 2.1 stack defines the cardinality of the APP_TIMELINE_SERVER to be
> "0-1", which means that zero or 1 instances of this service can be present in
> the cluster when Yarn is used. This cardinality was selected because the
> APP_TIMELINE_SERVER was considered a technical preview in HDP 2.1, and so was
> not required by the HDP 2.1 stack. This is why a Blueprint can be processed
> without the ATS, even if blueprint validation is left on.
> The BlueprintConfigurationProcessor class includes the following static
> references to the APP_TIMELINE_SERVER process:
> "// APP_TIMELINE_SERVER
> yarnSiteMap.put("yarn.timeline-service.address", new
> SingleHostTopologyUpdater("APP_TIMELINE_SERVER"));
> yarnSiteMap.put("yarn.timeline-service.webapp.address", new
> SingleHostTopologyUpdater("APP_TIMELINE_SERVER"));
> yarnSiteMap.put("yarn.timeline-service.webapp.https.address", new
> SingleHostTopologyUpdater("APP_TIMELINE_SERVER"));"
> The BlueprintConfigurationProcessor needs to be modified such that the
> topology substitution phase for these properties is not attempted when the
> APP_TIMELINE_SERVER is not included in an HDP 2.1 Blueprint.
> This problem will likely be constrained to the HDP 2.1 stack, since the ATS
> will likely have a cardinality of "1" in future stack definitions after HDP
> 2.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
