You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/03/01 13:52:45 UTC

[jira] [Commented] (AMBARI-20208) Atlas kafka servers should be configured using kafka listeners.

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

Hadoop QA commented on AMBARI-20208:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12855355/AMBARI-20208_1.patch
  against trunk revision .

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

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {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/10824//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/10824//console

This message is automatically generated.

> Atlas kafka servers should be configured using kafka listeners.
> ---------------------------------------------------------------
>
>                 Key: AMBARI-20208
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20208
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Vishal Suvagia
>            Assignee: Vishal Suvagia
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20208_1.patch, AMBARI-20208.patch
>
>
> Atlas kafka listeners should be configured to use the port value configured in kafka-broker listeners, instead of the port property.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)