[jira] [Commented] (AMBARI-12718) AMS is doing a (Select *) for certain point in time metrics from Dashboard page

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-12718:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12749835/AMBARI-12718.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-metrics/ambari-metrics-timelineservice.

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

This message is automatically generated.

> AMS is doing a (Select *) for certain point in time metrics from Dashboard page
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-12718
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12718
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Blocker
>             Fix For: 2.1.1
>
>         Attachments: AMBARI-12718.patch
>
>
> API calls for certain point in time metrics are fetching data for 1 day.
> API:
> {code}
> http://hostname:6188/ws/v1/timeline/metrics?metricNames=dfs.FSNamesystem.MissingReplOneBlocks%2Cdfs.FSNamesystem.TransactionsSinceLastCheckpoint%2Cdfs.FSNamesystem.MillisSinceLastLoadedEdits%2Cdfs.FSNamesystem.SnapshottableDi rectories%2Cdfs.FSNamesystem.LastCheckpointTime%2Cdfs.FSNamesystem.TotalFiles%2Cmaster.Master.QueueCallTime_median%2Cdfs.FSNamesystem.ExpiredHeartbeats%2Cdfs.FSNamesystem.PostponedMisreplicatedBlocks%2Cdfs.FSNamesystem.LastWrittenTransactionId%2Cdfs.FSNamesystem.Snapshots%2Cjvm.JvmMetrics.MemHeapCommittedM%2Cdfs.FSNamesystem.TransactionsSinceLastLog Roll%2Cmaster.Server.averageLoad%2Cjvm.JvmMetrics.MemHeapUsedM%2Cdfs.FSNamesystem.PendingDataNodeMessageCount%2Cmaster.AssignmentManger.ritCount%2Cdfs.FSNamesystem.StaleDataNodes&hostname=namenode_hostnamel&appId=NAMENODE
> {code}
> Returned result on a cluster > 1 day old takes very long time.
> The call should return 1 latest value for each metric vs all values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)