[jira] [Created] (AMBARI-7988) Blueprints export fails to include Yarn Timeline service properties when defaults are used

["Robert Nettleton (JIRA)" <ji...@apache.org>]

Robert Nettleton created AMBARI-7988:
----------------------------------------

             Summary: Blueprints export fails to include Yarn Timeline service properties when defaults are used
                 Key: AMBARI-7988
                 URL: https://issues.apache.org/jira/browse/AMBARI-7988
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 1.7.0
            Reporter: Robert Nettleton
            Assignee: Robert Nettleton
             Fix For: 1.7.0


If a Blueprint is exported from a running cluster in Ambari, the following properties are not included in the exported Blueprint:

yarn.timeline-service.address,
yarn.timeline-service.webapp.address,
yarn.timeline-service.webapp.https.address

These properties are not included if the stack defaults are not overridden, which is likely a common case for the Yarn Timeline serivce.  

If these server properties are overridden with host name information prior to cluster start, then these properties do appear in the exported blueprint, with the relevant hostname information removed.

The problem occurs when the defaults are used with this Yarn service.  The service configuration defaults to "0.0.0.0", a special IP address used to indicate that a service listens on all network interfaces on a given machine.  Since this address is slightly different than a normal host address, it must be handled differently by the Blueprint configuration processor.  

If the default "0.0.0.0" IP address is used for these defaults in the Yarn Timeline Service, the Blueprint configuration processor should allow these configuration properties to be included in the exported Blueprint.  

The current config processor will remove these properties, since no valid hostname is found during the export process.  

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)