[
https://issues.apache.org/jira/browse/AMBARI-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14951332#comment-14951332
]
Hadoop QA commented on AMBARI-13376:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12765809/AMBARI-13376_3.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 12 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/3942//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3942//console
This message is automatically generated.
> Prioritize point in time queries to JMX endpoints
> -------------------------------------------------
>
> Key: AMBARI-13376
> URL: https://issues.apache.org/jira/browse/AMBARI-13376
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, stacks
> Affects Versions: 2.1.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13376_3.patch
>
>
> - Find all point in time queries supported by both JMX and AMS
> - Priority order is JMX first, so all quries should goto JMX first and then
> remaining to AMS
> - The JMX data is latest and should be the only source of truth for point in
> time queries
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
