ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Speidel (JIRA)" <>
Subject [jira] [Resolved] (AMBARI-7458) Some HA Config Properties not visible after Blueprint Export of running cluster
Date Wed, 24 Sep 2014 17:23:36 GMT


John Speidel resolved AMBARI-7458.
    Resolution: Fixed

merged to trunk

> Some HA Config Properties not visible after Blueprint Export of running cluster
> -------------------------------------------------------------------------------
>                 Key: AMBARI-7458
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.6.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>             Fix For: 1.7.0
> Once Namenode High-Availability is enabled on a running cluster started by Ambari, an
attempt to export a Blueprint based on this cluster will be missing two properties:
> "fs.defaultFS" from core-site.xml
> "hbase.rootdir" from hbase-site.xml
> The properties are not included in the exported Blueprint due to an error in the Blueprint
Configuration Processor.  Any properties during the export process that should include host
information but do not will be removed from the configuration maps for the exported Blueprint.

> Generally, this is the correct way to process these configuration properties, but a few
properties (including the two listed above) can use references to HA "nameservices", rather
than refer to a specific hostname.  
> The current BlueprintConfigurationProcessor's export logic needs to be updated to account
for the case of some properties either containing host information or a nameservice reference.
 In Ambari 1.7, the fix for this will likely be a short-term fix.  In the longer term, it
would be more desirable to include metadata in the stack definitions that allow the Blueprint
processor to determine which properties are affected by enabling HA.  
> I'm working on a patch to fix this, and will be submitting it soon. 

This message was sent by Atlassian JIRA

View raw message