ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15192) Atlas Integration : Atlas Server fails to properly start if Zookeeper isn't started first
Date Sat, 27 Feb 2016 00:36:18 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-15192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170200#comment-15170200
] 

Hadoop QA commented on AMBARI-15192:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12790225/AMBARI-15192.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/5598//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5598//console

This message is automatically generated.

> 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