[
https://issues.apache.org/jira/browse/AMBARI-13521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969534#comment-14969534
]
Hadoop QA commented on AMBARI-13521:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12768023/AMBARI-13521_2.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 2 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/4040//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4040//console
This message is automatically generated.
> Allow Monitors/Agents to be configured to communicate with a collector that
> is behind a VIP
> -------------------------------------------------------------------------------------------
>
> Key: AMBARI-13521
> URL: https://issues.apache.org/jira/browse/AMBARI-13521
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, stacks
> Affects Versions: 2.1.1
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Blocker
> Fix For: 2.1.3
>
> Attachments: AMBARI-13521.patch, AMBARI-13521_2.patch
>
>
> Currently the address of the AMS Collector is automatically picked up from
> the host assignment to the component. When AMS is used in the active-passive
> configuration then the hostname of the collector should be explicitly
> specifiable. That way, it can be configured to have the collector traffic
> flow through the VIP.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
