[
https://issues.apache.org/jira/browse/AMBARI-16227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Nettleton updated AMBARI-16227:
--------------------------------------
Status: Patch Available (was: In Progress)
> Blueprint deployments with LogSearch should fail if Zookeeper is not present
> ----------------------------------------------------------------------------
>
> Key: AMBARI-16227
> URL: https://issues.apache.org/jira/browse/AMBARI-16227
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16227.patch
>
>
> Currently, deploying a Blueprints cluster that includes the new LogSearch
> components does not have the appropriate amount of validation during the
> initial POST of the Blueprint.
> If a Blueprint is POST-ed to ambari-server with LogSearch components, but
> without a Zookeeper server instance ("ZOOKEEPER_SERVER"), the POST will
> succeed, but the Cluster deployment based on this Blueprint will eventually
> fail, as all LogSearch components require access to the cluster's Zookeeper
> quorum.
> The stack definition metadata for the LogSearch service should be updated, so
> that the dependency on ZOOKEEPER_SERVER is explicitly required. If a
> Blueprint includes LogSearch, but does not include the ZOOKEEPER_SERVER
> instance, this should result in an error thrown back to a cluster attempting
> to POST the invalid Blueprint.
> While is is possible to deploy valid LogSearch clusters with Blueprints
> currently, this type of validation is required in order to assist the
> creation of new Blueprints, to ensure that the proper required components are
> included in the cluster.
> 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)
