ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Speidel (JIRA)" <>
Subject [jira] [Resolved] (AMBARI-7242) Unnecessary conditional dependencies added to Blueprint when NAGIOS_SERVER included
Date Thu, 11 Sep 2014 20:14:34 GMT


John Speidel resolved AMBARI-7242.
    Resolution: Fixed

merged to trunk

> Unnecessary conditional dependencies added to Blueprint when NAGIOS_SERVER included
> -----------------------------------------------------------------------------------
>                 Key: AMBARI-7242
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.6.1
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>             Fix For: 1.7.0
> If an Ambari Blueprint is posted that includes the "NAGIOS_SERVER" component in a host
group definition, some YARN-related dependencies are automatically added to the blueprint,
even if YARN is not referenced in the blueprint.  
> This means that a blueprint may have slightly different content after a POST, so that
the GET will return a blueprint with more components than originally desired.  
> This problem is caused by the fact that some dependencies in Ambari are conditional,
and this type of dependency is not yet modeled in the Ambari Stack Definitions.  Whenever
the NAGIOS_SERVER component is included, the dependencies associated with that component (including
YARN_CLIENT, TEZ_CLIENT, etc) are also added to the blueprint during the creation process.
> The Blueprint handling code needs to be modified in order to handle this conditional
type of dependency in the short term.  As a longer-term fix, eventually these dependencies
should be included in the stack definitions. 
> I'll be posting a patch shortly that addresses this problem.  

This message was sent by Atlassian JIRA

View raw message