ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Nettleton (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-7738) Blueprints: Cluster deployment attempt in HDP 2.1 fails without Yarn APP_TIMELINE_SERVER
Date Fri, 10 Oct 2014 19:15:34 GMT
Robert Nettleton created AMBARI-7738:
----------------------------------------

             Summary: 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


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)

Mime
View raw message