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/15 02:52:34 UTC

[jira] [Updated] (AMBARI-9139) Deploying Kafka via a Blueprint without Ganglia fails

     [ https://issues.apache.org/jira/browse/AMBARI-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Nettleton updated AMBARI-9139:
-------------------------------------
    Attachment: AMBARI-9139.patch

Uploaded initial version of patch for this issue. 

> Deploying Kafka via a Blueprint without Ganglia fails
> -----------------------------------------------------
>
>                 Key: AMBARI-9139
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9139
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9139.patch
>
>
> Deploying a Blueprint that includes Kafka 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 a kafka-broker.xml property that references the GANGLIA_SERVER component. The configuration processor needs to be modified so that Kafka 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)