ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Beerbower (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-15192) Atlas Integration : Atlas Server fails to properly start if Zookeeper isn't started first
Date Fri, 26 Feb 2016 21:43:18 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-15192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tom Beerbower updated AMBARI-15192:
-----------------------------------
    Attachment: AMBARI-15192.patch

> 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)

Mime
View raw message