Robert Nettleton created AMBARI-7507:
----------------------------------------
Summary: Oozie external DB properties are exported with hostname
information
Key: AMBARI-7507
URL: https://issues.apache.org/jira/browse/AMBARI-7507
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 1.6.0
Reporter: Robert Nettleton
Assignee: Robert Nettleton
Fix For: 1.7.0
The Blueprint export configuration processor incorrectly handles the case of
two Oozie configuration properties that are only used when Oozie is configured
to point towards an existing MYSQL database, rather than have Ambari create the
DB during the cluster startup.
The properties involved are:
"oozie_existing_mysql_host"
and
"oozie.service.JPAService.jdbc.url"
Currently, after a cluster starts up with these configuration properties set to
an external DB server, an attempt to export a Blueprint based on this cluster
will cause these properties to be included in the Blueprint. These properties
will include the hostname information for the external DB.
In general, this is not very useful for a Blueprint, since this information may
vary from cluster to cluster, so the Blueprint processor should remove these
properties from the Blueprint during the export process. Since the external DB
server is not part of a defined Host group, the processor cannot assign a
logical host group name instead of the actual host name, so removing the
properties is the only way to keep this host information out of the exported
Blueprint.
These Oozie properties are generally either pointing to a default, local,
in-memory DB, or to an external DB, to the normal property update mechanism
won't really apply here.
The BlueprintConfigurationProcessor needs to be updated so that these
properties are removed from the exported Blueprint during the export process.
I'm working on a fix for this, and will be submitting a patch soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
