[
https://issues.apache.org/jira/browse/AMBARI-15192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173364#comment-15173364
]
Hudson commented on AMBARI-15192:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #4411 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4411/])
AMBARI-15192 - Atlas Integration : Atlas Server fails to properly start
(tbeerbower:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8b6fa3931470ff7ddaedbdf4f6a4ca25426006d6])
* ambari-server/src/main/resources/stacks/HDP/2.3/role_command_order.json
> Atlas Integration : Atlas Server fails to properly start if Zookeeper isn't
> started first
> -----------------------------------------------------------------------------------------
>
> Key: AMBARI-15192
> URL: https://issues.apache.org/jira/browse/AMBARI-15192
> Project: Ambari
> Issue Type: Bug
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Attachments: AMBARI-15192.patch
>
>
> When Atlas Server version 0.6 is started, it creates a Kafka consumer which
> attempts to connect to Zookeeper. The atlas startup script returns a status
> of 0 immediately, not waiting for the server to actually start successfully.
> Because Atlas now has a dependency on Kafka and ZK, this needs to be
> expressed in role_command_order.json for UI installs. But since we use the
> same stack definition for both Atlas 0.5 and 0.6 installs and only 0.6 has
> the Kafka and ZK dependencies we need to ensure that we don't negatively
> affect 0.5 installs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
