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

Hadoop QA commented on AMBARI-22491:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12898677/AMBARI-22491.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 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

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

    {color:red}-1 core tests{color}.  The test build failed in 
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12701//artifact/patch-work/testrun_ambari-web.txt]
 

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/12701//console

This message is automatically generated.

> Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-22491
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22491
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.2
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Blocker
>             Fix For: 2.6.1
>
>         Attachments: AMBARI-22491.patch
>
>
> When moving a Metrics Collector, a ZooKeeper Server is installed on the 
> target host along with the Metrics Collector. This ZooKeeper Server is added 
> and quorum can be upset in large clusters, and the customer was not intending 
> to have a ZooKeeper server on the target directory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to