You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Robert Nettleton (JIRA)" <ji...@apache.org> on 2015/01/08 02:43:35 UTC

[jira] [Created] (AMBARI-9036) Deploying Storm via a Blueprint without Ganglia fails

Robert Nettleton created AMBARI-9036:
----------------------------------------

             Summary: Deploying Storm via a Blueprint without Ganglia fails
                 Key: AMBARI-9036
                 URL: https://issues.apache.org/jira/browse/AMBARI-9036
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.0.0
            Reporter: Robert Nettleton
            Assignee: Robert Nettleton
             Fix For: 2.0.0


Deploying a Blueprint that includes Storm will fail if the "GANGLIA_SERVER" component is not included in the Blueprint.

The deployment error is:

"{ "status" : 400, "message" : "Unable to update configuration property with topology information. Component 'GANGLIA_SERVER' is not mapped to any host group or is mapped to multiple groups." }"

The Blueprint Configuration processor currently fails in this deployment scenario, while attempting to perform hostname substitution for some storm-site properties that reference the GANGLIA_SERVER component.  The configuration processor needs to be modified so that Storm can be deployed via a Blueprint without Ganglia. 

I'm working on a fix for this, and will be submitting a patch shortly. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)